From: Jonathan Morton <chromatix99@gmail.com>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,
"babel-users@lists.alioth.debian.org"
<babel-users@lists.alioth.debian.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Harald Geyer <harald@ccbib.org>
Subject: Re: [Cerowrt-devel] [Babel-users] Why we are discussing ARM [was: Cross-compiling to armhf]
Date: Sun, 26 Jun 2016 22:58:08 +0300 [thread overview]
Message-ID: <71E65F1D-C3EA-4124-A88A-F540F3E64150@gmail.com> (raw)
In-Reply-To: <20160626190244.GB29321@lud.polynome.dn42>
> On 26 Jun, 2016, at 22:02, Baptiste Jonglez <baptiste@bitsofnetworks.org> wrote:
>
>> Do you know how the Ethernet is hooked to the SoC? I could be wrong, but
>> I don't think Allwinner SoCs include GMII.
>
> I suggest you look at the schematics (here for LIME2):
>
> https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/A20-OLinuXino-LIME2/A20-OLinuXino-Lime2_Rev_G.pdf
>
> Looking quickly, this looks like a SPI interface. I'm really not a
> hardware expert though, so you'd better check yourself.
It looks like GMII to me. That’s a good thing.
SPI would be extremely unlikely - it just doesn’t have that sort of bandwidth, and I’ve never heard of it being used to attach Ethernet before. It appears that some of the pins used for GMII on the AllWinner are shared with one of the SPI interfaces (and a serial UART) - they can be used for one purpose or the other, but not both. This is quite common practice in the embedded world.
- Jonathan Morton
next prev parent reply other threads:[~2016-06-26 19:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 23:54 [Cerowrt-devel] beaglebone green wireless boards now available Dave Taht
2016-06-22 11:31 ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Juliusz Chroboczek
2016-06-22 12:08 ` [Cerowrt-devel] [Babel-users] " Benjamin Henrion
2016-06-22 13:10 ` [Cerowrt-devel] Cross-compiling to armhf Juliusz Chroboczek
2016-06-22 13:15 ` Benjamin Henrion
2016-06-22 20:38 ` Juliusz Chroboczek
2016-06-22 16:38 ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Dave Taht
2016-06-23 22:10 ` Juliusz Chroboczek
2016-06-23 22:45 ` Dave Taht
2016-06-23 22:57 ` Juliusz Chroboczek
2016-06-23 23:13 ` Dave Taht
2016-06-24 0:02 ` [Cerowrt-devel] Why we are discussing ARM [was: Cross-compiling to armhf] Juliusz Chroboczek
2016-06-24 2:37 ` Jonathan Morton
2016-06-24 11:04 ` Juliusz Chroboczek
2016-06-24 16:36 ` Eric Johansson
2016-06-24 20:27 ` David Lang
[not found] ` <E1bH8oe-0000Wv-EO@stardust.g4.wien.funkfeuer.at>
2016-06-26 17:59 ` [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2016-06-26 19:02 ` Baptiste Jonglez
2016-06-26 19:58 ` Jonathan Morton [this message]
2016-06-26 20:03 ` Juliusz Chroboczek
2016-06-23 23:20 ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Jonathan Morton
2016-06-23 23:27 ` Dave Taht
2016-06-23 23:42 ` Dave Taht
2016-06-24 16:25 ` Eric Johansson
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=71E65F1D-C3EA-4124-A88A-F540F3E64150@gmail.com \
--to=chromatix99@gmail.com \
--cc=babel-users@lists.alioth.debian.org \
--cc=baptiste@bitsofnetworks.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=harald@ccbib.org \
--cc=jch@pps.univ-paris-diderot.fr \
/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