From: linux@baker-net.org.uk (Adam Baker)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch v2 3/3] kirkwood: Add iconnect support
Date: Tue, 1 May 2012 23:55:38 +0100 [thread overview]
Message-ID: <201205012355.38598.linux@baker-net.org.uk> (raw)
In-Reply-To: <878vhdbtk1.fsf@lebrac.rtp-net.org>
On Monday 30 April 2012, Arnaud Patard wrote:
> Adam Baker <linux@baker-net.org.uk> writes:
>
> Hi,
>
> > On Thursday 26 April 2012, Arnaud Patard wrote:
> >> Adam Baker <linux@baker-net.org.uk> writes:
> >>
> >> Hi,
> >>
> >> > On Wednesday 18 April 2012, Arnaud Patard wrote:
> >> >> Add support for Iomega Iconnect system.
> >> >>
> >> >> Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
> >> >
> >> > Arnaud,
> >> >
> >> > I have so far been unable to get a kernel to boot with your patches. I
> >> > just get
> >> >
> >> > Uncompressing Linux... done, booting the kernel.
> >>
> >> hm. sounds weird. Are you sure that you have the DTB appended to your
> >> kernel image ?
> >
> > Yes, if I don't append the DTB and I set ArcNumber to 1682 then it boots
> > using the ref board setup, if the DTB is appended then it doesn't boot
> > (I configured the kernel to support iconnect, dreamplug and RD-88F6281)
>
> hm. ok. Can you provide your uImage/kernel config/modules/ and which
> sources you've used... so that I can try to reproduce / boot your kernel?
>
Arnaud has spotted that my kernel config was missing CONFIG_SERIAL_OF_PLATFORM
which is why I was getting no output from it. After fixing that I've got a
working system, therefore
Tested-By: Adam Baker <linux@baker-net.org.uk>
I have verified that all of the LED options work, that the reset and OTB
buttons generate the expected codes (I think the reason Iomega chose odd SW_
values is simply those are the first 2 defined values in linux/input.h) and that
the mtd partitions start at the correct offsets for what they claim to contain
(although the last one might make more sense called root rather than boot).
I've verified that the WLAN interface works but not tested wired ethernet.
Unfortunately CONFIG_SERIAL_OF_PLATFORM has dependencies so it wouldn't be a
good idea for CONFIG_MACH_ICONNECT_DT to select it. There could be some value
in it making the default value for CONFIG_SERIAL_OF_PLATFORM=y.
Regards
Adam
next prev parent reply other threads:[~2012-05-01 22:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 21:16 [patch v2 0/3] Kirwood: Add Iomega Iconnect support Arnaud Patard (Rtp)
2012-04-18 21:16 ` [patch v2 1/3] kirkwood/orion: fix orion_gpio_set_blink Arnaud Patard (Rtp)
2012-04-18 21:16 ` [patch v2 2/3] orion/kirkwood: create a generic function for gpio led blinking Arnaud Patard (Rtp)
2012-04-18 21:16 ` [patch v2 3/3] kirkwood: Add iconnect support Arnaud Patard (Rtp)
2012-04-25 22:45 ` Adam Baker
2012-04-26 10:23 ` Arnaud Patard (Rtp)
2012-04-29 23:11 ` Adam Baker
2012-04-30 6:52 ` Arnaud Patard (Rtp)
2012-05-01 22:55 ` Adam Baker [this message]
2012-05-11 11:54 ` Arnaud Patard (Rtp)
2012-05-11 13:02 ` Jason Cooper
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=201205012355.38598.linux@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--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).