Re: USB Ethernet hang on eject
Of course not. I never do that with pccards :-) That's why I asked it :-) It shouldn't be necessary. When I do that, as a work around, I find that I can pull the plug. How hard is it to fix the way that the ethernet driver reads the MII registers in the interrupt context? Hard, but probably not impossible. Especially with threads in interrupts or worker threads, it should be possible. Task queue might be a solution as well, although I guess the problem is that the action is blocking, and task queue might not handle that very well. A worker thread for the ethernet drivers is probably the simplest solution. Nick To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: USB Ethernet hang on eject
This is a known problem. It has to do with the way the ethernet driver reads the MII registers in interrupt context. Did you try and ifconfig delete the interface first? Nick On Tue, 29 May 2001, Warner Losh wrote: I'm getting a hang on eject of the USB Ethernet card that I have. aue0: SMC, Inc EZ USB/Ethernet Converter, rev 1.10/1.01, addr 2 aue0: Ethernet address: 00:e0:29:59:fe:11 miibus0: MII bus on aue0 When I remote the card, I get USB errors. I also have an interrupt storm from the USB controller. I set a breakpoint on the interrupt handler and get over and over again Anything that I can do to help track down the problem here? This is current as of May 18th, 12:00:00 MDT. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- The USB for FreeBSD project. [EMAIL PROTECTED] http://www.etla.net/~n_hibma/usb/usb.pl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GENERIC kernel hangs at boot (uhci-related)
The reason it is failing is that the assigned IRQ is 0 or 255. If I can't assume that that setup is done, I might as well start implementing PCI resource allocation, because that is what is missing here. The problem is not that the PCI device is not initialised, but that the device is assigned a bogus irq (0/255) by the BIOS. It is allocated and setup correctly as far as I can see from other PCI drivers. But then it never fires, which is correct, because there is no such thing as irq 0 or 255. And that's were the driver freezes, waiting for an interrupt that never comes and never times out or at least times out very slowly. What John Polstra is suggesting is to check for these bogus values and reject the device such that the boot will complete. Or am I misunderstanding you completely, Mike? Nick The bottom line is this; in your driver, ask for the resources that you need. If you don't get them, you fail. The PCI bus infrastructure is being worked on to improve your chances of getting these resources; it's not something that a driver writer should be worrying about per se. And I should probably have added; the assumptions you can make about the state of your device are very few. There is a *very* good chance that your device will *just* have been powered up, and had the BARs set to something sane. That's it. You should not make any assumptions about setup done by the BIOS, firmware, etc. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- The USB for FreeBSD project. [EMAIL PROTECTED] http://www.etla.net/~n_hibma/usb/usb.pl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP ata ioctls changed
Which ports break? Nick On Thu, 17 May 2001, Søren Schmidt wrote: The ioctl to the ata driver has changed a bit, please make sure your kernel and userland are in sync. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- The USB for FreeBSD project. [EMAIL PROTECTED] http://www.etla.net/~n_hibma/usb/usb.pl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: hid_report_size() prototype wrong in both -stable and -current
Concidental. The code that is in libusb is also present in the kernel. Nick On Tue, 17 Apr 2001, Nick Sayer wrote: usb.h != libusb.h NetBSD has a stupid naming convention. Use libusb.h in FreeBSD. Ok. That's as may be, but then why are there prototypes for libusb calls in dev/usb.h? The prototypes are correct as is. They may be in libusb.h, but the prototype for that function in sys/dev/usb.h is mysterious. -- The USB for FreeBSD project. [EMAIL PROTECTED] http://www.etla.net/~n_hibma/usb/usb.pl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: hid_report_size() prototype wrong in both -stable and -current
usb.h != libusb.h NetBSD has a stupid naming convention. Use libusb.h in FreeBSD. The prototypes are correct as is. The changes to libusb made in CURRENT have not been backported to STABLE (yet). Nick On Tue, 17 Apr 2001, Nick Sayer wrote: The definition of hid_report_size() differs between -stable and -current (as to its prototype), yet /usr/src/sys/dev/usb.h shows no difference between -stable and -current, and is wrong in either case. This is causing some heartburn for -current builders of the xmame port. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- The USB for FreeBSD project. [EMAIL PROTECTED] http://www.etla.net/~n_hibma/usb/usb.pl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB compact flash reader diffs
send them to me. Thanks. Nick On Mon, 2 Apr 2001, Phil Knaack wrote: Greetings: I made some quirk-diffs to umass.c and scsi_da.c to make the USB Microtech CameraMate compactFlash/smartMedia reader work under 5.0-current. Someone want the diffs or should I just PR it? Cheers, Phil -- -- Phil Knaack __ Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- The USB for FreeBSD project. [EMAIL PROTECTED] http://www.etla.net/~n_hibma/usb/usb.pl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
