> On Tue, May 22, 2007 at 08:01:53AM -0400, email@example.com wrote:
>> I've noticed that besides kernel complied from the Debian 2.6.18, I
>> get any other kernel (vanilla from kernel.org or the separate linux-MIPS
>> repository) to boot on my O2.
>> If you need beta testers, I can try, but it will take a day or so
>> (compiling on the O2 is slow).
> Sounds almost like you're building an excessibly large kernel
> A realistic kernel config will crosscompile within a few minutes on a
> modest machine such as a 3GHz / 1GB P4-class PC.
I could never get cross-compiling to work, so I've been doing all my
compiling directly on the R5K 300 Mhz CPU in my O2. If there is an easy
way to get this to work, I'd be very thankful for some pointers. Might my
trying to compile on the actual machine be why I can't seem to use any
source other than Debian's 2.6.18?
> But to lessen the pains of your aching CPU, here's a binary tarball:
Thanks. I installed the kernel and arcboot was able to load it, but
nothing showed up on the screen. Does this have framebuffer support? In
was also unable to ssh in. Does this kernel have the necessary support for
that? It didn't fault at boot (like most of my nonbootable kernel do) and
I did hear the standard startup hard drive activity, so things may be
working. I was also able to get a response from the power button to
correctly reboot. Sadly I lack the necessary null modem cable for a serial
console (if this was the only interface you configured). If you can crank
out a new one with framebuffer support just as quickly, I'll gladly give
it a whirl.
>> Finally, I've been working on the PCI Legacy IO issue (progress is sadly
>> slow - don't have a fully compiling patchset yet), would this patch be
>> relevant since its also an O2 sysfs issue?
> The two issues are entirely unrelated.
Nice to know.