From: tibor@harsszegi.com (Tibor Harsszegi)
To: linux-arm-kernel@lists.infradead.org
Subject: NSA310 + DT
Date: Wed, 10 Jul 2013 18:57:16 +0200 [thread overview]
Message-ID: <51DD926C.1010205@harsszegi.com> (raw)
In-Reply-To: <20130710165342.GA31692@lunn.ch>
Cool, keep you posted.
> On Wed, Jul 10, 2013 at 06:40:43PM +0200, Tibor Harsszegi wrote:
>> Hello Andrew,
>>
>> I did a:
>>
>> ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make clean
>> ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make kirkwood_defconfig
>> ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make zImage
>> ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make dtbs
>> cat arch/arm/boot/zImage arch/arm/boot/dts/kirkwood-nsa310-tdc.dtb > /tmp/X
>> mv /tmp/X arch/arm/boot/zImage
>> ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make uImage
>> ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make modules
>>
>> [attached .config]
>>
>> copied the uImage over the NSA310, rebooted.
>> Good news: console is back
> Great. Probably was OF_SERIAL_PLATFORM
>
>> Bad news: LEDs still don't work (all green), kernel stops (tried
>> forcing rootfstype=ext4, didn't help)
> Ah, O.k. EXT4 is not part of kirkwood_defconfig. Hence it cannot mount
> the root fs.
>
> Please could you use make menuconfig and include it into the kernel
> image. I will also update the patch later.
>
> LEDs are not working because the GPIO driver is not loading.
> I will see if i can spot an obvious typo etc.
>
> Andrew
next prev parent reply other threads:[~2013-07-10 16:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51DC564A.8050002@harsszegi.com>
2013-07-09 19:36 ` NSA310 + DT Andrew Lunn
2013-07-09 20:21 ` Andrew Lunn
2013-07-10 0:53 ` tibor at harsszegi.com
2013-07-10 6:23 ` Andrew Lunn
2013-07-10 8:42 ` tibor at harsszegi.com
2013-07-10 13:41 ` Andrew Lunn
[not found] ` <51DD8E8B.2040505@harsszegi.com>
2013-07-10 16:44 ` Tibor Harsszegi
2013-07-10 16:53 ` Andrew Lunn
2013-07-10 16:57 ` Tibor Harsszegi [this message]
2013-07-10 17:13 ` Tibor Harsszegi
2013-07-10 17:15 ` Tibor Harsszegi
2013-07-10 17:23 ` Andrew Lunn
2013-07-10 17:29 ` Tibor Harsszegi
2013-07-10 1:01 ` tibor at harsszegi.com
2013-07-10 7:37 ` Andrew Lunn
2013-07-10 8:43 ` tibor at harsszegi.com
[not found] ` <51DEDB32.4080101@harsszegi.com>
2013-07-11 16:44 ` gpio_blink_set + Kirkwood Andrew Lunn
2013-07-11 18:32 ` Tibor Harsszegi
2013-07-11 18:37 ` Jason Cooper
2013-07-11 18:52 ` Tibor Harsszegi
2013-07-11 19:44 ` Jason Cooper
2013-07-29 17:05 ` NSA310 + DT Finn Hoffmann
2013-07-29 19:21 ` Jason Cooper
2013-07-29 20:43 ` Andrew Lunn
[not found] ` <51F78DA6.8010307@uni-bremen.de>
[not found] ` <20130730144752.GR24782@lunn.ch>
[not found] ` <20130730172407.3aab15c6@skate>
[not found] ` <51F7EBB9.7000504@uni-bremen.de>
[not found] ` <20130730191943.49f8070c@skate>
2013-07-30 18:36 ` Andrew Lunn
2013-07-30 19:31 ` Finn Hoffmann
2013-07-30 19:42 ` Andrew Lunn
2013-07-30 21:23 ` Thomas Petazzoni
2013-07-31 9:14 ` Thomas Petazzoni
2013-07-31 9:43 ` Finn Hoffmann
2013-07-31 9:51 ` Thomas Petazzoni
2013-07-31 11:41 ` Finn Hoffmann
2013-07-31 11:47 ` Thomas Petazzoni
2013-07-31 16:45 ` Andrew Lunn
2013-08-01 8:01 ` Finn Hoffmann
2013-08-01 16:04 ` Andrew Lunn
2013-08-01 20:43 ` Finn Hoffmann
2013-08-02 8:35 ` Finn Hoffmann
2013-08-02 8:46 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51DD926C.1010205@harsszegi.com \
--to=tibor@harsszegi.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).