[EMAIL PROTECTED] said:
More problematic is that if I stick such prinks into arch/i386/kernel/
irq.c handle_IRQ_event(), that stops seeing interrupts too ... even
timer irqs. They happen right up to the point of lockup though.
At this point (in fact long before this) I would get out the
Is there any objection to the remover patch I submitted a while ago
to the hotplug and usb-devel lists? It seems to help my design of
applications that use USB devices, so I would like to get it integrated
into the main hotplug repository. If there are specific objections,
I can address them.
[EMAIL PROTECTED] said:
The patch looks fishy to me. Does it work when the root is mounted
read-only?
That's why it does its work in /var/run.
--
Steve WilliamsThe woods are lovely, dark and deep.
[EMAIL PROTECTED] But I have promises to keep,
[EMAIL PROTECTED]
[EMAIL PROTECTED] said:
You are missing the point. Root is mounted read-only upon boot, and
hotplug running at that time does not work if it attempts to write or
create files.
You are right, I completely forgot about that. Piffle!
But wait! Don't all the other demons, such as bind, inetd,
[EMAIL PROTECTED] said:
USB initialization needs to be a lot earlier than that, so USB input
devices can be used for system maintenance if necesarry (like fscks,
interactive startup of services etc)
Well, yeah. But what does this have to do with the hotplug scripts?
I even see in the
[EMAIL PROTECTED] said:
/var may be hot plugged. Life is interesting.
Maybe too interesting.
--
Steve WilliamsThe woods are lovely, dark and deep.
[EMAIL PROTECTED] But I have promises to keep,
[EMAIL PROTECTED]and lines to code before I sleep,
I'm rather accustomed to lists that fill my mailbox until I can't
stand it, so I'm a little surprised how quiet the linux-hotplug
list is. I posted a patch to the hotplug scripts to support hot
remove of USB devices, but I haven't heard praise or protest in a
few days, so I'll present it here
I'm writing an application that works with a USB device. The device
itself is expected to be plugged and unplugged during the lifetime
of the application, so I'm looking for a way to follow the state of
the device. It's a GTK application, I have no problem with using
timers.
[EMAIL
Is there something like a programmer's guide for libusb? I have a new
piece of hardware (flash programmer) that I want to write software for.
I can cope with the ez-usb chip on board just fine, but basically I'm
in need of a Getting Started with libusb document.
Incidentally, I've also seen on
