Y_SIZE(errorcodes); ++i) { > +if
(num == errorcodes[i].err || num == -errorcodes[i].err) {
why not taking the abs value only once, instead of duplicate comp on
each iteration ?
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
i...@
via unionfs+friends)
4. it shall be swappable (if swap is enabled)
In that scenario, these in-kernel headers would just one consumer,
I can imagine lots of others.
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
i...@metux.net -- +49-151-27565287
e same place where the .ko's live.
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
i...@metux.net -- +49-151-27565287
the horizon ?
> Practically speaking, the only universal mechanism is to bake something
> into the kernel image or one of its modules.
Aha, and when do we start moving widget toolkits and html renderers
into the kernel ? :o
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
i...@metux.net -- +49-151-27565287
mainline first. (and, of course, ban all
proprietary binary-only kernel modules).
> Now for kernel modules, there's another image called the "vendor
> image" which is flashed onto the vendor parition, this is where kernel
> modules go.
Okay, then why not just putting a tarball there ?
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
i...@metux.net -- +49-151-27565287
-tools ?
Sorry, but the whole Android build machinery is so *extremly* huge,
that adding yet another tiny tool, which is in all relevant distros
for aeons, really shouldn't be a problem worth even talking about.
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
i...@metux.net -- +49-151-27565287
nowing the headers for the kernel with
Fix fastboot to support initrd or use a remote filesystem ?
I'm doing embedded development all the day, and one of the first things
I usually set up for a project is an fully automatic netboot (or at
least usb boot). Shouldn't be so hard, and is
s-a-kernel-module-I-promise.ko /usr/src/linux/include :-).
We should ask coreutils folks to add an ELF encapsulation to tar ;-)
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
i...@metux.net -- +49-151-27565287