From: andy@warmcat.com (Andy Green)
To: linux-arm-kernel@lists.infradead.org
Subject: Ethernet in a cold climate / SMDK6410
Date: Mon, 28 Dec 2009 18:40:00 +0000 [thread overview]
Message-ID: <4B38FB80.9050609@warmcat.com> (raw)
Hi -
I broke out my old SMDK6410 last night and tried linux-next then Ben's
git on it (currently next-s3c64xx-updates) started from s3c6410 Qi / SD
Card boot.
It's basically happy but OTG doesn't seem workable for Ethernet gadget.
Well it's dumping a lot of debug messages so I guess maybe that's
where it got up to, fair enough.
I eyeballed the back of the SMDK and I see a CS8900A and a SMSC LAN9115
both sitting there, coming out on separate RJ45s. When I look at the
machine init file, I see Mark added
static struct resource smdk6410_smsc911x_resources[] = {
[0] = {
.start = 0x18000000,
.end = 0x18000000 + SZ_64K - 1,
.flags = IORESOURCE_MEM,
},
...
What is the deal with that in terms of SDMK settings and assumptions
about bootloader prepping nCS signals? SMDK docs I have let me twiddle
switches and get "ethernet" connected to various selects. What does
0x18000000 represent and how should the board be set so CS8900A doesn't
crash the party?
After some debug-by-printk, I see smsc911x probe is failing with:
smsc911x: BYTE_TEST: 0xFFFFFFFF
smsc911x: top 16 bits equal to bottom 16 bits
smsc911x: This may mean the chip is set for 32 bit while the bus is
reading 16 bit
smsc911x: init failed
So I am guessing the nCS pin is not configured, something is missing a
clock... one of the dozens of mini DIP switches is "wrong"?
-Andy
next reply other threads:[~2009-12-28 18:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 18:40 Andy Green [this message]
2009-12-28 19:00 ` Ethernet in a cold climate / SMDK6410 Mark Brown
2009-12-28 19:07 ` Andy Green
2009-12-28 19:22 ` Mark Brown
2009-12-28 19:45 ` Andy Green
2009-12-28 20:21 ` Mark Brown
2009-12-28 20:46 ` Andy Green
2009-12-28 22:44 ` Mark Brown
2009-12-29 10:04 ` Andy Green
2009-12-29 12:33 ` Mark Brown
2009-12-29 12:50 ` Andy Green
2009-12-30 13:16 ` Mark Brown
2009-12-30 13:37 ` Ethernet / SD Boot Andy Green
2009-12-31 12:27 ` Mark Brown
2009-12-31 12:59 ` Andy Green
2010-01-04 16:26 ` Ben Dooks
2010-01-04 17:28 ` Andy Green
2010-01-04 17:40 ` Russell King - ARM Linux
2010-01-04 18:09 ` Andy Green
2010-01-05 14:17 ` Marc Zyngier
2010-01-04 18:49 ` Jamie Lokier
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=4B38FB80.9050609@warmcat.com \
--to=andy@warmcat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.