[Debian-eeepc-devel] Some experiences with kernel 2.6.31

[Luca Niccoli]

2009/10/11 Alan Jenkins <sourcejedi.lkml at googlemail.com>:

> But there is only one init method to run :-/.

You're right, I was still thinking about the rfkill delay, but that
shall go away.

> That way, we
>  - load eeepc-laptop as normal when udev starts, but avoid blocking
> the rest of the boot process on it
>  - avoid a confusing "blacklist" entry which isn't really a blacklist
>  -  allow the user to add "blacklist eeepc-laptop" and have it work as normal

Ok, I made this try:

Add to /etc/modprobe.d/eeepc.conf:
install eeepc_laptop modprobe --ignore-install eeepc_laptop $CMDLINE_OPTS &

Applied the attached patch the /etc/init.d/eee-acpi-scripts:
it makes the change you suggested (I only added --ignore-install to
the modprobe call, otherwise it forks to background), plus it makes
SHEngine calls fork to background, as they're awfully slow (up to 4s
on my 901).
These two changes together make a whole lot of difference on my system.

> Then we should also change the eeepc-laptop driver to initialise
> asynchronously when it is built in to the kernel.  Otherwise building
> it into the kernel will slow down the boot process, which is
> unpleasantly counter-intuitive.

You mean making the whole module init an async call?

> Does that make sense?  Do you want to work on this yourself, or should
> I add it to my TODO list?

I think the kernel stuff could be a bit hard to merge upstream...
For the debian scritps, is any maintainer reading this thread?
What do they think?

Cheers,
Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eeepc-acpi-scripts.patch
Type: text/x-diff
Size: 1305 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/attachments/20091011/a8452a74/attachment.patch>