src/sys/dev/fdc/fdc.c, branch release/8.2.0 FreeBSD source tree MFC r197945: 2010-03-27T17:56:45+00:00 Edward Tomasz Napierala trasz@FreeBSD.org 2010-03-27T17:56:45+00:00 168d1f006bba2eaab15d79d8395871a381eea17e Orphaning provider with EXDEV seems weird; perhaps the author meant ENXIO here? 
Orphaning provider with EXDEV seems weird; perhaps the author meant
ENXIO here?
MFC r198520, r198857: fdc(4) module unload fixes 2009-12-23T11:35:25+00:00 Jaakko Heinonen jh@FreeBSD.org 2009-12-23T11:35:25+00:00 48c7a876968b0ab4418bf0c511e260d032410cc8 PR: kern/104079 Approved by: trasz (mentor) 
PR:		kern/104079
Approved by:	trasz (mentor)
With the fdc control device disappearing some 5 years ago, it is no 2009-06-24T19:30:31+00:00 Joerg Wunsch joerg@FreeBSD.org 2009-06-24T19:30:31+00:00 3fdc1d5c487e0702b4890584f1195d567ec9ed31 longer useful for the FD_STYPE and FD_SOPTS ioctls to insist on being issued on a writable file descriptor. Otherwise, there's no longer a chance to set the drive type or options when a read-only medium is present in the drive, as there is no way to obtain a writable fd then. 
longer useful for the FD_STYPE and FD_SOPTS ioctls to insist on being
issued on a writable file descriptor.  Otherwise, there's no longer a
chance to set the drive type or options when a read-only medium is
present in the drive, as there is no way to obtain a writable fd then.
- Revive fdc(4) per-device flag 0x10, which was removed in r1.284[1]. 2008-11-15T01:43:34+00:00 Jung-uk Kim jkim@FreeBSD.org 2008-11-15T01:43:34+00:00 c884498f0bde4c8a8b7924a4a9fe63d561a8c7d5 - If the flag is set and auto-select fails, assume disk is not present. - Set disk empty flag only when the floppy controller reset is needed. It fixes regression introduced in r1.311, which prevented it from ignoring errors. Now fdformat(1) and dd(1) with conv=noerror option can continue when read/write errors occur as they should. - Do not retry disk probing as it is extremely slow and pointless. - Move the disk probing code into a separate function. - Do not reset disk empty flag if write-protect check fails somehow. PR: kern/116538[1] 
- If the flag is set and auto-select fails, assume disk is not present.
- Set disk empty flag only when the floppy controller reset is needed.
It fixes regression introduced in r1.311, which prevented it from ignoring
errors.  Now fdformat(1) and dd(1) with conv=noerror option can continue
when read/write errors occur as they should.
- Do not retry disk probing as it is extremely slow and pointless.
- Move the disk probing code into a separate function.
- Do not reset disk empty flag if write-protect check fails somehow.

PR:		kern/116538[1]
The wakeup() line from the rev. 1.319 is wrong and reintroduces 2008-01-11T16:50:52+00:00 Konstantin Belousov kib@FreeBSD.org 2008-01-11T16:50:52+00:00 89a828fde94cfb83da985c9d727c28e0bac0b100 a panic race on module unload. The wakeup() is internal to kproc_exit/kthread_exit. The correct fix is to fix the msleep() in detach to sleep on fdc->fdc_thread instead of &fdc->fdc_thread. Noted and reviewed by: jhb Pointy hat to: kib MFC after: 1 week 
a panic race on module unload. The wakeup() is internal to
kproc_exit/kthread_exit. The correct fix is to fix the msleep() in
detach to sleep on fdc->fdc_thread instead of &fdc->fdc_thread.

Noted and reviewed by:	jhb
Pointy hat to:	kib
MFC after:	1 week
Fix unload of the fdc.ko: 2008-01-11T11:53:04+00:00 Konstantin Belousov kib@FreeBSD.org 2008-01-11T11:53:04+00:00 fc9f8bcf4f25461d922731c3e114fbc76b45600e Wakeup the thread doing the fdc_detach() when the fdc worker thread exits [1]. Write access to the write-protected floppy shall call device_unbusy() to pair the device_busy() in the fd_access() [2]. PR: 116537 [1], 116539 [2] MFC after: 1 week 
Wakeup the thread doing the fdc_detach() when the fdc worker thread exits [1].
Write access to the write-protected floppy shall call device_unbusy() to
pair the device_busy() in the fd_access() [2].

PR:	116537 [1], 116539 [2]
MFC after:	1 week
Rename the kthread_xxx (e.g. kthread_create()) calls 2007-10-20T23:23:23+00:00 Julian Elischer julian@FreeBSD.org 2007-10-20T23:23:23+00:00 3745c395ecae17ef47be82433463d561629220b0 to kproc_xxx as they actually make whole processes. Thos makes way for us to add REAL kthread_create() and friends that actually make theads. it turns out that most of these calls actually end up being moved back to the thread version when it's added. but we need to make this cosmetic change first. I'd LOVE to do this rename in 7.0 so that we can eventually MFC the new kthread_xxx() calls. 
to kproc_xxx as they actually make whole processes.
Thos makes way for us to add REAL kthread_create() and friends
that actually make theads. it turns out that most of these
calls actually end up being moved back to the thread version
when it's added. but we need to make this cosmetic change first.

I'd LOVE to do this rename in 7.0  so that we can eventually MFC the
new kthread_xxx() calls.
Always protect the kthread flags with the lock and close a race with 2007-02-27T17:16:52+00:00 John Baldwin jhb@FreeBSD.org 2007-02-27T17:16:52+00:00 5f6fcd82a2fe44a9a330cd655028e5ea35d0c00a module unload and kthread_exit(). MFC after: 3 days 
module unload and kthread_exit().

MFC after:	3 days
Use tsleep() rather than msleep() with a NULL mtx parameter. 2007-02-23T23:06:10+00:00 John Baldwin jhb@FreeBSD.org 2007-02-23T23:06:10+00:00 6e50e38fcce8c444397d635c689c842a5af05dae 






o break newbus api: add a new argument of type driver_filter_t to
2007-02-23T12:19:07+00:00

Paolo Pisati
piso@FreeBSD.org

2007-02-23T12:19:07+00:00

ef544f631226436ef590825881e7a28369df82f6

  bus_setup_intr()

o add an int return code to all fast handlers

o retire INTR_FAST/IH_FAST

For more info: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=465712+0+current/freebsd-current

Reviewed by: many
Approved by: re@





  bus_setup_intr()

o add an int return code to all fast handlers

o retire INTR_FAST/IH_FAST

For more info: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=465712+0+current/freebsd-current

Reviewed by: many
Approved by: re@