Bill Nottingham ([EMAIL PROTECTED]) said:
Here you go; sorts them into two piles (networking and block), and expands
the symbol list to catch some of the missing modules such as ahci and
some of the wireless drivers.
... committed.
Bill
___
On Fri, 2007-07-27 at 12:28 -0400, Bill Nottingham wrote:
Jon Masters ([EMAIL PROTECTED]) said:
On Thu, 2007-07-26 at 22:13 -0400, Bill Nottingham wrote:
Frankly, I think this sort of computation should either a) be done in
modutils, so
that it's upstream for any kernel b) just be
On Fri, 2007-07-27 at 12:28 -0400, Bill Nottingham wrote:
Jon Masters ([EMAIL PROTECTED]) said:
On Thu, 2007-07-26 at 22:13 -0400, Bill Nottingham wrote:
Frankly, I think this sort of computation should either a) be done in
modutils, so
that it's upstream for any kernel b) just be
On Fri, 2007-07-27 at 13:43 -0400, Bill Nottingham wrote:
Jeremy Katz ([EMAIL PROTECTED]) said:
Actually, the more I think about it... is this really appropriate for all
upstream m-i-t users? Especially since it will probably be a never-ending
task of adjusting the symbol list to find
Jeremy Katz ([EMAIL PROTECTED]) said:
Depends on how many copies of the qlogic driver there are ;-)
RHEL live CDs? What's that?
(Actually, I lied - drivers/block + drivers/scsi is 1.3M compressed.)
I mean, I guess I can just do manual twiddling to rule out things that
aren't under
Jeremy Katz ([EMAIL PROTECTED]) said:
If
it's done at runtime, you can handle whatever kernel you happen to get,
even if it's not one of ours.
There are plenty of constraints we have around kernel configuration.
Asking for a file to be shipped with the kernel which tells us a little
On Fri, 2007-07-27 at 14:03 -0400, Bill Nottingham wrote:
Jeremy Katz ([EMAIL PROTECTED]) said:
If
it's done at runtime, you can handle whatever kernel you happen to get,
even if it's not one of ours.
There are plenty of constraints we have around kernel configuration.
Asking for
