On Mon, Jun 02, 2008 at 09:55:08PM +0200, Bart Samwel wrote: > Hmmmm. If it does horrible things in those cases, I need > something that absolutely only does stuff when it's safe. > Don't want to break other people's systems! But if you > can provide something that works only for the dock in > absence of the bay, then I'd be very happy to include it.
I'm taking a look at this right now with kernel 2.6.25-2-686. Things are looking good: booting attached to the dock, I can undock by prodding the /sys/devices/platform/dock.0/undock, redocking happens automatically. All attached devices: USB subsystem, ethernet, display, disappeared on remove and reappeared on dock, automatically. [ ideally my display would reconfigure itself to be smaller: my tft is 1280x1024, my lcd is 1024x768 and shows the upper corner of this size after undocking. But I don't think that's an acpi-support issue ] I tried inserting the bay after boot - the sys/bus/platform/bay.0 tree appeared, and present under that heirarchy correctly represents whether the bay is there or not. I haven't convinced the contents of the bay to appear yet (a CD-ROM device) --but nothing has broken. You need to include the event and shellscript that I attached to the LP bug (with all the commented out code stripped - it's no use) for the hotkey to work on my thinkpad (and probably all other thinkpads) I'm going to try booting with the bay and see what difference that makes, then check the kernel history to see whether there's been any fixes applie since 25 in the bay module that might be relevant. I'll prepare a patch with the shellscript/event tidied up for the most recent acpi-support package at the end of tonight, plus any stuff needed for bay support too. -- Jon Dowland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
