hotplug ** DISCONTINUED **

[johnbock]

kann man das Nachfolgende bitte einmal in deutsch bekommen?

It's for development of further filesystem types support for the hotplug replacement... If you need to know, you know

 

[Lemur]

hi johnbock,

many thx for your great work!

It's possible to use an usb printer with your future hotplug patch?
If I connect a printer at my hub, syslog will say:

Jun 23 04:52:23 fritz user.info kernel: usb 1-1.1: new full speed USB device using ahci and address 6
Jun 23 04:52:23 fritz local0.debug hotplug: starting hotplug chain 'usb.add'
Jun 23 04:52:23 fritz local0.debug hotplug: starting hotplug chain 'usb.add'
Jun 23 04:52:23 fritz local0.err hotplug: unrecognized interface '7/1/2'

Currently I use hotplug 0.6.0a with usbroot, at a 7170, rev. 29.04.57-freetz-devel-2342M.

Kind regards
Lemur

 

[johnbock]

It's possible to use an usb printer with your future hotplug patch?

The design of hotplug 0.6a has a deficite conserning character devices.
I'm currently working on an alternative for hotplug that will allow char nodes/devices (including printers) to be more easily setup for the system.

Current status of the alternative:

• support for block devices as in hotplug 0.6a
• support for stick n' surf devices as in hotplug 0.6a
• support for bluetooth devices
• support for serial-usb adapters
• allows alias and configuration options while loading modules
  will not survive reboot (need help here)
• automatic module chain removal while disconnecting device
• better support for configure, plug and play (pray)
• better development/debug support
• event chain documentation
• and a few other things that only purists can appreciate

I don't own an usb printer, so that may take a while till it's properly supported. However, I'm pretty far along now and it may be released for review soon, very soon

Once it passes review, I image it won't be too long until it's somewhere in the freetz repository.

 

[poruid]

# allows alias and configuration options while loading modules
will not survive reboot (need help here)

When the problem is related to storing the modules configuration to flash, then maybe an implementation for a writable non-volatile filesystem such as usbroot could be tried first.

BTW: usbroot was not compatible with the new hpc; any changes in this respect?

 

[johnbock]

Because your patch removes (comments out) the /dev/sd* entries in the device.table

BTW: usbroot was not compatible with the new hpc; any changes in this respect?

Yes, the alternate development uses bb's mdev for all event processing. mdev can scan the hardware and setup devices/nodes that are present before hotplug processing begins. CAVEAT, need to lock out certain events during scanning.

 

[johnbock]

Support for this thread has been discontinued by the author. This hotplug implementation has been abandoned in favor for mdev.