7 messages in org.freebsd.freebsd-archRe: Where should I put ar71xx_* modules?| From | Sent On | Attachments |
|---|---|---|
| Adrian Chadd | Jan 8, 2012 3:41 pm | |
| Stefan Bethke | Jan 8, 2012 11:58 pm | |
| Adrian Chadd | Jan 9, 2012 12:38 am | |
| Stefan Bethke | Jan 9, 2012 12:52 am | |
| Adrian Chadd | Jan 9, 2012 1:03 am | |
| John Baldwin | Jan 9, 2012 4:57 am | |
| Adrian Chadd | Jan 9, 2012 9:43 am |
| Subject: | Re: Where should I put ar71xx_* modules? | |
|---|---|---|
| From: | Stefan Bethke (st...@lassitu.de) | |
| Date: | Jan 8, 2012 11:58:57 pm | |
| List: | org.freebsd.freebsd-arch | |
Am 09.01.2012 um 00:42 schrieb Adrian Chadd:
Hi,
In order to fit an lzma'd kernel in 892 kilobytes of flash (that's 892 * 1024 bytes), I've needed to break out a few things into modules.
I'd like to commit a couple of modules - for example, ar71xx_ehci/ar71xx_ohci for USB stuff - but I don't want them built for anything other than ar71xx builds. Thus I don't see the reason for putting them in sys/modules/Makefile.
They build fine if they're included in MODULES_OVERRIDE in the relevant kernel config file.
So is it ok to just commit some modules in sys/modules/ which aren't in the Makefile, and instead include them in the relevant SoC kernel configs so they're built? Or is there some other tradition for doing this?
Why would it hurt to have them connected to the standard build? Doe the
tinderboxes build modules?
Stefan
-- Stefan Bethke <st...@lassitu.de> Fon +49 151 14070811
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "free...@freebsd.org"