Christian,
and removed some not needed drivers. The kernel is now 3698472 bytes big.
I still find that huge, but it allowed me to boot without a memfile to
reduce the RAM! Alas, no SCSI support for the B2060...
Not entirely unexpected.
yup. CONFIG_SCSI_ZORRO7XX is enabled, will this be the new driver?
No, that's a different chipset, not ESP.
The official Debian package fails to cross-compile when building the
hid-microsoft module, maybe its time to disable that? Probably this is not
set in the m68k config, but in the "main" debian config. I am not sure if I
can override that, it may be easier to build kernels (for testing and the
Why not? Just add another m68k patch that removes this option from
the defconfig used.
As far as I remember, the config is combined of a generic config, an m68k
config, and an amiga config. Each file set only part of the total config,
And you can't patch the generic config? Not that I'd want to submit that
as a patch against the kernel source, of course.
probably so that the kernels across all arches support more of less the same
features. Thats a good idea, but I think many drivers are useless for the
buildds, by removing them the kernel can fit into memory again, just barely.
That sort of stuff should be built as modules anyway.
The HID drivers seem to be enabled in the official kernel, which runs on
kullervo, I don't seem to be able to switch off just the microsoft one.
Maybe by modifying the generic config, but I am afraid the magical package
building breaks again, genconfig.py does not run on my testing box, not sure
why. In Geert's tree, memcmp is not used in the driver, thats probably why
this one builds:
@@ -47,9 +46,9 @@
rdesc[559] = 0x45;
}
/* the same as above (s/usage/physical/) */
- if ((quirks & MS_RDESC_3K) && *rsize == 106 &&
- !memcmp((char []){ 0x19, 0x00, 0x29, 0xff },
- &rdesc[94], 4)) {
+ if ((quirks & MS_RDESC_3K) && *rsize == 106 && rdesc[94] == 0x19 &&
+ rdesc[95] == 0x00 && rdesc[96] == 0x29 &&
+ rdesc[97] == 0xff) {
rdesc[94] = 0x35;
rdesc[96] = 0x45;
}
Looks like it - we'd either need memcmp, or use above patch to sanitize
the HID driver.
I don't think I have seen that patch on m68k-queue though.
No idea really - how are the kernel packages built otherwise?
I tried: 4.5 Building a custom kernel from Debian kernel source:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
with linux-source-3.8, which is easier to modify than the linux source
package (it does not run genconfig for one). Cross-compiling is easy:
make ARCH=m68k CROSS_COMPILE=m68k-linux-gnu- deb-pkg
but it creates the same failure due to memcmp. I wonder how the debian
packages have been built, or maybe the cross-compilers are outdated on my
system?
That might be the case - I've had to patch around stuff that was
suddenly expected to be provided by the compiler on occasion.
The kernel packages are built with python magic, it seems. kernel-package
does not seem to be used anymore. You do not look at the kernel for four
and a half years, and BOOM, suddenly everything has changed!
I'm amazed that I can still build Geert's tree with gcc 3.3.6 :-)
Anyway, I'll poke around a bit on IJ's virtual machine, maybe it does
work there.
Cheers,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
