Hi,

That's not the problem. The problem is that there is a kernel module
(correction, not the kernel itself, but rather the driver for the CS5536
"companion chip"*) that needs modifications compiled into it in order to
(re)activate the IDE header after the BIOS cuts it off.

I know how to use Google, too. I hoped that your problem could be fixed through the kernel command line, but I just confirmed that this is not possible. No need to bash me for that. :-(

Kernel drivers live inside the kernel source tree, so changing a driver soure file is equivalent to changing a kernel source file itself, which is the same as changing the kernel.

Whether you compile a driver as a kernel module (i.e. a separate file which gets loaded into the running kernel at runtime) or not (i.e. integrated into the kernel binary itself and loaded at kernel initialization time) is a matter of preference. This is what kernel configuration is all about: [Y]es, [N]o, or [M]odule.

Even then, there's a pretty sizable chance that I won't be able to do what I
need to do... I seem to recall having some significant issues getting that
particular system to boot in the first place.

I would avoid using kernel modules and build everything which is integrated (i.e. not hotpluggable) into the kernel. Hotpluggable stuff (USB drivers) is a case-by-case decision.

I don't know what to think of your knowledge. On one side, you seem to know quite a bit, on the other side you behave like you have no clue of what you are doing. It's hard for me to know what I can trust you to do correctly on your own given a few instructions and where hand-holding is necessary.

Just on a side note, mailing lists are not live communication channels. They are archived, and in a few weeks nobody cares about your endeavours to get things to work. But people might care about facts and solutions to problems. Please keep focused. Searching through 40+ mails of chat is a pain for anyone not living in the same time zone. Especially when there is no useful information /at all/.

IRC is the perfect medium for live discussions, step-by-step hand-holding, "you can't build a kernel, but I can build one for you and you can test it" setups and similar things. But please don't spam the list uselessly.

Best Regards,
Sebastian,
going to bed now (4:30am local time).
_______________________________________________
Openchrome-devel mailing list
Openchrome-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/openchrome-devel

Reply via email to