16 messages in org.freebsd.freebsd-hackersHow disable attachment of sio(4) driv...| From | Sent On | Attachments |
|---|---|---|
| Frank Behrens | Oct 21, 2005 1:36 am | |
| M. Warner Losh | Oct 21, 2005 9:07 am | |
| John Baldwin | Oct 21, 2005 9:37 am | |
| M. Warner Losh | Oct 21, 2005 10:36 am | |
| Marcel Moolenaar | Oct 21, 2005 12:10 pm | |
| Bernd Walter | Oct 21, 2005 1:39 pm | |
| Daniel O'Connor | Oct 21, 2005 11:31 pm | |
| Bernd Walter | Oct 22, 2005 5:18 am | |
| Daniel O'Connor | Oct 22, 2005 6:00 am | |
| Frank Behrens | Oct 22, 2005 8:17 am | |
| Frank Behrens | Oct 22, 2005 8:17 am | |
| M. Warner Losh | Oct 22, 2005 9:33 am | |
| Bernd Walter | Oct 24, 2005 5:32 am | |
| Frank Behrens | Oct 24, 2005 5:46 am | |
| John Baldwin | Oct 24, 2005 8:42 am | |
| M. Warner Losh | Oct 24, 2005 9:27 am |
| Subject: | How disable attachment of sio(4) driver to device? | |
|---|---|---|
| From: | Bernd Walter (tic...@cicely12.cicely.de) | |
| Date: | Oct 24, 2005 5:32:56 am | |
| List: | org.freebsd.freebsd-hackers | |
On Sat, Oct 22, 2005 at 05:16:49PM +0200, Frank Behrens wrote:
Warner, John and others,
thanks for your fast responses.
John Baldwin <jh...@freebsd.org> wrote on 21 Oct 2005 12:16:
But you could hack the sio(4) driver to check its IO port and return ENXIO if it has a certain value, for example.
Yes, this would not be a problem for me. But I want to publish my driver as port and make it for the user as easy as possible. That includes not the need for building a new kernel.
M. Warner Losh <im...@bsdimp.com> wrote on 21 Oct 2005 10:06:
Another "soltution" is to not have sio in your kernel while you are debugging your driver.
Well, you used already the quotes. It is not an option for me, because my system has no keyboard and monitor attached and the serial console is my only way to see the panic messages. ;-)
Another solution would be to have your driver use the tty layer instead of banging the hardware directly, if that is compatible with the goals of your driver. This solution isn't in quotes because for some class of devices (say a keyboard driver for a sun or apple newton keyboard that does serial), it might be the right one.
Hm, this looks even more complicated and has more overhead. To show shortly my requirements: The protocol is for an eib driver, (further information on http://www.sax.de/~frank/eib4bsd/), it uses 9600 baud on serial line. If the PC wants to send a telegram it resets RTS and has to poll CTS. If CTS is active the transmission of one byte is possible. If the last bit is sent (transceiver shift empty!) the PC sets RTS and waits until CTS is inactive. Then a new handshake can start and a transmission of about 30 bytes must be finished in 130 ms. IMHO this can be handled only in an interrupt routine with low overhead.
PEI-16 design is evil IMO and PEI-10 capable BCU are less common. I already planed support for EIB using Weinzierl's USB hardware, it's just a matter of time. I dislike the protocol beeing based on UHID, but that's how it is standardized, at least other EIB USB devices are likly to work as well. Usually UHID is prefered so people don't have to write Windows-driver.
-- B.Walter BWCT http://www.bwct.de ber...@bwct.de in...@bwct.de