Buildroot a linux 2.6.26-lab126 kernal. (3.3)

[twobob]

Originally Posted by knc1

Keep notes.
If interested, keep them on a new wiki page at mmg.

Note: The new page does not have to be "linked in" anywhere, you can always find every page you ever created in your MyTiki section (if turned on in MyTikireferences).

Yep, I have been making extensive - mail based - notes.

When cav gets his thread up about DX unbricking I will wait to see what is fact and fiction....

Then go from there

[twobob]

Well. Still haven't quite got qt (4.8.3 OOTB via Buildroot) to run on my 3... sigh.. I do however have a huge pile of stuff just waiting to test with once I crack the fb/driver issues.

Looking thru the docs / qtkindle / hawhill / k3chess stuff again for some inspiration. : )

after a very long day getting the DX tamed into submission (wow that's twitchy work) I think it's time for the sack.

tomorrow the world!!! oh alright, maybe not, but definitely some tea.
and that's close enough.

[geekmaster]

Originally Posted by twobob

...
tomorrow the world!!! oh alright, maybe not, but definitely some tea.
and that's close enough.

HTTP = Hot Tea Transfer Protocol?

[twobob]

To demonstrate how close...

Qt 4.8.3 - very nearly... on a 3

Sigh. don't suppose a developer fancies coming round my gaff?
I can provide tea...

Never mind. I'll carry on then.

[twobob]

Originally Posted by NiLuJe

@twobob: Never played with the Kernel, but you might want to give the 'depmod with the custom modules put in the right place in /lib/modules' thing a go, if you managed to force-inject a custom-built module once.

On the TC front, more or less what knc1 said, except I'd stay away from multilib/interwork TC, unless you want a wall with an embossed version of your head on it ^^. And the things I mentioned/are commented in my x-tc script if you're using something recent and targetting the K2/3 (kill gcc's ssp: -fno-stack-protector in CFLAGS & CXXFLAGS, kill glibc's fortify: -U_FORTIFY_SOURCE in CPPFLAGS).

Hi mate. can we have a uname -a from the k2?

Thanks

[NiLuJe]

[root@kindle root]# uname -a
Linux kindle 2.6.22.19-lab126 #3 PREEMPT Thu Jan 13 18:13:20 PST 2011 armv6l unknown

[root@kindle root]# /lib/libc.so.6 
GNU C Library stable release version 2.5, by Roland McGrath et al.
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.1.2.
Compiled on a Linux 2.6.15 system on 2008-06-10.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        GNU libio by Per Bothner
        NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
        Native POSIX Threads Library by Ulrich Drepper et al
        Support for some architectures added on, not maintained in glibc core.
        BIND-8.2.3-T5B
Thread-local storage support included.
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.

[root@kindle root]# cat /proc/usid | cut -b -4     
B003

[root@kindle root]# cat /etc/version.txt 
System Software Version: 010-TNM0.9-055537
Thu Jan 13 18:17:49 PST 2011

[root@kindle root]# cat /etc/prettyversion.txt 
Kindle 2.5.8 (~~otaVersion~~)

[root@kindle root]# cat /proc/cpuinfo 
Processor       : ARMv6-compatible processor rev 4 (v6l)
BogoMIPS        : 1593.88
Features        : swp half thumb fastmult vfp edsp java 
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant     : 0x0
CPU part        : 0xb36
CPU revision    : 4
Cache type      : write-back
Cache clean     : cp15 c7 ops
Cache lockdown  : format C
Cache format    : Harvard
I size          : 16384
I assoc         : 4
I line length   : 32
I sets          : 128
D size          : 16384
D assoc         : 4
D line length   : 32
D sets          : 128

Hardware        : Mario Platform
Revision        : 31020
Serial          : "B003XXXXXXXXXXXX"

[root@kindle root]# cat /proc/meminfo | head -n 1
MemTotal:       127128 kB

[knc1]

Super!
We can work with that for certain.

[twobob]

Thanks so very much.

That would explain why I couldn't find a reference to anything earlier than a 2.6.22.19 kernel in reference to the K2 / DX /K3

K2:
[root@kindle root]# uname -a

Linux kindle 2.6.22.19-lab126 #3 PREEMPT Thu Jan 13 18:13:20 PST 2011 armv6l unknown

DX:
[root@kindle root]# uname -a

Linux kindle 2.6.22.19-lab126 #3 PREEMPT Thu Jan 13 18:13:20 PST 2011 armv6l unknown

K3: (3.4 IIRC)
[root@kindle root]# uname -a

Linux kindle 2.6.26-rt-lab126 #5 Sat Sep 1 14:28:26 PDT 2012 armv6l GNU/Linux

So, 2.6.22.19 is our "line in the sand."

Thanks again!!

[twobob]

Originally Posted by geekmaster

Don't the kindles already have lua?

It transpires. No, not really all of them. but they will have now

Lol talk about slow comeback!

[twobob]

Originally Posted by knc1

Pardon me if I mention the obvious, no insult intended, but in case you missed it:
In the top level directory of the Buildroot tree, enter:
make manual

**Then** you will have something to read that is supposed to match the version your using.

hardly insulted.

And here I am months and months later searching for this exact post to find the command again!

So. Sir. I salute you.

[knc1]

Just noted the dates -
This thread is a year old.
Have we been messing up this forum with our posts that long? Hard to believe.

[twobob]

Seems like : )

I don't regret it.

[thatworkshop]

I was harvesting this thread to see a reason why an old Sourcery was used but couldn't find why! Can a recent version, say 2013.05, be used?

[twobob]

It was used as that was the Toolkit that more or less identically matched the Toolset "of the day" when 3.x was made...

You may have to do some fancy Flags to ensure that newer symbols aren't referenced. TBH this is beyond my scope of knowledge at this time. You would need Niluje or similar for such Ninjaness.

I do know that KoReader? (or similar, I forget which) uses the newest Toolchains and builds compliant binaires. Possibly check out how they manage it.

[NiLuJe]

IIRC, if you want to build *modules* without flashing the kernel, then, yeah, you'll need more or less the exact same TC amazon used.

If you intend to fully flash kernel + modules, then I think you can go with whatever you prefer . (And if you do, check the few comments in my cross-compile env setup, there are a few links to easy stuff that it might be neat to backport).