Date: Thu, 23 Jul 2009 13:53:17 +0800
From: Eugene Grosbein eu...@kuzbass.ru
Sender: owner-freebsd-sta...@freebsd.org
On Thu, Jul 23, 2009 at 10:14:18AM +0800, Sagara Wijetunga wrote:
If you conversant in this area, could you help us to identify what is/are
the exact function/s in
on 23/07/2009 17:14 Kevin Oberman said the following:
If Linux detects media insertion instantly or Windows detects media
insertion instantly (which I can confirm), there is some signal
available, so looking at the Linux driver should provide a clue as to
what to look for and that can be added
on 23/07/2009 18:33 Peter C. Lai said the following:
GEOM should pick up the state change, but the bug may continue to exist
because the CF reader is tagged as a storage device with invalid media
when umass attaches to it on startup; there wasn't a really good way to
actually enumerate the
GEOM should pick up the state change, but the bug may continue to exist
because the CF reader is tagged as a storage device with invalid media
when umass attaches to it on startup; there wasn't a really good way to
actually enumerate the slice table upon insertion because the device
does not send
Eugene Grosbein wrote:
On Thu, Jul 23, 2009 at 10:14:18AM +0800, Sagara Wijetunga wrote
If you conversant in this area, could you help us to identify what is/are
the exact function/s in which program/s to look into identify the media
insertion activity, so that we can generate relevant devd
On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote:
Hi FreeBSD community
The SCSI device (eg. da1s1) is not created automatically upon a CF card
plug in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI
device (eg. da1s1) is created automatically if I reboot the computer
Milan Obuch writes:
On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote:
Hi FreeBSD community
The SCSI device (eg. da1s1) is not created automatically upon a CF card
plug in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI
device (eg. da1s1) is created automatically if I
Milan Obuch wrote:
On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote:
Hi FreeBSD community
The SCSI device (eg. da1s1) is not created automatically upon a CF card
plug in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI
device (eg. da1s1) is created automatically if I
On Wed, 2009-07-22 at 11:52 +0800, Sagara Wijetunga wrote:
Hi Milan, thanks for the reply.
Yep, your suggestion works but it simply unacceptable for end users. We are
the makers of the Tomahawk Desktop (http://www.tomahawkcomputers.com/).
Anybody in the FreeBSD community care to develop
On Wednesday 22 July 2009 08:11:23 Sagara Wijetunga wrote:
Milan Obuch writes:
On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote:
Hi FreeBSD community
The SCSI device (eg. da1s1) is not created automatically upon a CF card
plug in on an USB multi-card reader on FreeBSD 7.2
On Wednesday 22 July 2009 09:38:50 Ivan Voras wrote:
[ snip ]
After the CF card is plugged in:
$ ls -l /dev/ | grep da
crw-r- 1 rootoperator0, 105 Jul 22 13:18 da0
crw-r- 1 rootoperator0, 106 Jul 22 13:18 da1
crw-r- 1 rootoperator0, 107 Jul 22
Milan Obuch wrote:
On Wednesday 22 July 2009 09:38:50 Ivan Voras wrote:
[ snip ]
After the CF card is plugged in:
$ ls -l /dev/ | grep da
crw-r- 1 rootoperator0, 105 Jul 22 13:18 da0
crw-r- 1 rootoperator0, 106 Jul 22 13:18 da1
crw-r- 1 rootoperator0,
Milan Obuch writes:
On Wednesday 22 July 2009 08:11:23 Sagara Wijetunga wrote:
Milan Obuch writes:
On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote:
Hi FreeBSD community
The SCSI device (eg. da1s1) is not created automatically upon a CF card
plug in on an USB multi-card reader on
Ivan Voras writes:
Milan Obuch wrote:
On Wednesday 22 July 2009 09:38:50 Ivan Voras wrote:
[ snip ]
After the CF card is plugged in:
$ ls -l /dev/ | grep da
crw-r- 1 rootoperator0, 105 Jul 22 13:18 da0
crw-r- 1 rootoperator0, 106 Jul 22 13:18 da1
crw-r- 1
I have earlier posted my tests with Linux. All tests were done with same CF
cards and the very same multi-card reader on the same computer. They work on
Linux. That is, nothing wrong with the multi-card reader, it does it's job
of signaling well.
What makes you sure that Linux is using
Pete French writes:
I have earlier posted my tests with Linux. All tests were done with same CF
cards and the very same multi-card reader on the same computer. They work on
Linux. That is, nothing wrong with the multi-card reader, it does it's job
of signaling well.
What makes you sure
On Wed, Jul 22, 2009 at 10:20:27AM +0800, Sagara Wijetunga wrote:
My questions in this regards are:
1. Is this an error/bug in FreeBSD 7.2?
This is regression from pre-5.x days. In 4.x and earlier,
you can have static device nodes and access them just fine.
2. Or, does it require some
Eugene Grosbein writes:
On Wed, Jul 22, 2009 at 10:20:27AM +0800, Sagara Wijetunga wrote:
My questions in this regards are:
1. Is this an error/bug in FreeBSD 7.2?
This is regression from pre-5.x days. In 4.x and earlier,
you can have static device nodes and access them just fine.
2. Or,
On Thu, Jul 23, 2009 at 08:13:38AM +0800, Sagara Wijetunga wrote:
Hi Eugene, thanks for the reply. The issue we discussed is about internal
multi-card readers. For internal multi-card readers, the umassX created at
boot time. If there is media inside at boot time, the device node for
Eugene Grosbein writes:
On Thu, Jul 23, 2009 at 08:13:38AM +0800, Sagara Wijetunga wrote:
Hi Eugene, thanks for the reply. The issue we discussed is about internal
multi-card readers. For internal multi-card readers, the umassX created at
boot time. If there is media inside at boot time, the
On Thu, Jul 23, 2009 at 10:14:18AM +0800, Sagara Wijetunga wrote:
If you conversant in this area, could you help us to identify what is/are
the exact function/s in which program/s to look into identify the media
insertion activity, so that we can generate relevant devd event.
No, I'm not.
21 matches
Mail list logo
