static kernel and makepkg

lens · 2011-04-22 05:01:41

I have built a static kernel (i.e. no modules, all built in) but I can't see a way to make brcm 43xx into the kernel instead of a module. I searched but maybe didn't use the magic search word. I see a brcm in the driver/staging and tried that but it can't find the /lib/firmware/b43 which I created via b43-fwcutter.

I'm not sure how smart the linux kernel builds are and I will try putting the wl* src under the kernel/drivers and see what happens.

I really can't understand why computer makers limit their market space by making the hardware drivers propietary. Is it just due to competition? Zeal for commerce? Both?

lens · 2011-04-23 01:31:11

Looks like this has been done already. Although the package is marked out-of-date it seems that it will work with some changes.

http://aur.archlinux.org/packages.php/p … p?ID=34625

tomk · 2011-04-23 01:40:42

Read that PKGBUILD again - wl is being compiled as a module, not built-in.

lens · 2011-04-23 17:35:04

You're right, not sure why it's called a static kernel though. Am going to try another route.

Arch Linux

#1 2011-04-22 05:01:41

static kernel and makepkg

#2 2011-04-23 01:31:11

Re: static kernel and makepkg

#3 2011-04-23 01:40:42

Re: static kernel and makepkg

#4 2011-04-23 17:35:04

Re: static kernel and makepkg

Board footer