From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: DT changes for v3.17
Date: Fri, 27 Jun 2014 16:13:56 +0200 [thread overview]
Message-ID: <53AD7C24.5090408@gmail.com> (raw)
In-Reply-To: <20140627135932.GI32514@n2100.arm.linux.org.uk>
On 06/27/2014 03:59 PM, Russell King - ARM Linux wrote:
> On Fri, Jun 27, 2014 at 03:44:36PM +0200, Sebastian Hesselbarth wrote:
>> On 06/27/2014 03:39 PM, Jason Cooper wrote:
>>> On Fri, Jun 27, 2014 at 03:31:57PM +0200, Sebastian Hesselbarth wrote:
>>>> Also, production variants have their MAC address stored at 0xd0000 on
>>>> SPI flash. And while ES has PL2303 USB-to-UART, production use a
>>>> different brand, IIRC FTDI.
>>>
>>> Could you do a follow on patch adding a comment to this effect? The
>>> Debian guys will need this for flash-kernel and friends.
>>
>> I don't know if that information will be of any use at all.
>>
>> You cannot determine USB-to-UART type from CuBox but your host PC only.
>>
>> And I am not sure, if we want to rely on some six numbers stored on
>> SPI flash, i.e. there is no magic nor header to be really sure, it
>> is a MAC address.
>
> This is kind'a my point - you're confirming that you can't reliably
> tell which version you have by running something on the cubox itself.
> As Jason points out, there are those who need to choose the correct
> DT file when installing.
>
> So, this means that the user has to be asked. If users have to be
> asked, users need some way to identify the hardware that they're
> running on.
I get your point, but there is no way to automatically tell them apart.
IMHO, that is why cubox-dove.dts should represent the *production*
version.
> No, I didn't know until recently, because my Cubox was given to me by
> Nicolas Pitre a couple of years ago - that's the problem, the engineering
> samples may not be with the original people and therefore their origins
> may not be known.
It is printed on the box it came in ;)
Honestly, I consider it much more likely that someone who buys/owns an
ES is able to tell them apart than the other way round. And _you_ know
how to deal with the wrong dts, the other may not.
Sebastian
next prev parent reply other threads:[~2014-06-27 14:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 13:01 [GIT PULL] ARM: mvebu: DT changes for v3.17 Jason Cooper
2014-06-27 13:04 ` Russell King - ARM Linux
2014-06-27 13:31 ` Sebastian Hesselbarth
2014-06-27 13:39 ` Jason Cooper
2014-06-27 13:44 ` Sebastian Hesselbarth
2014-06-27 13:59 ` Russell King - ARM Linux
2014-06-27 14:13 ` Sebastian Hesselbarth [this message]
2014-06-27 14:46 ` Russell King - ARM Linux
2014-06-27 14:52 ` Sebastian Hesselbarth
2014-06-27 16:49 ` Jason Cooper
2014-06-27 17:36 ` Sebastian Hesselbarth
2014-06-28 14:54 ` Jason Cooper
2014-06-30 7:50 ` Sebastian Hesselbarth
2014-07-08 12:10 ` Jason Cooper
2014-06-27 13:37 ` Jason Cooper
2014-07-08 5:34 ` Olof Johansson
2014-07-08 11:57 ` Jason Cooper
2014-07-08 12:12 ` Russell King - ARM Linux
2014-07-08 12:46 ` Jason Cooper
2014-07-17 12:35 ` Jason Cooper
2014-07-18 13:29 ` Arnd Bergmann
2014-07-18 22:20 ` Olof Johansson
2014-07-08 12:53 ` Sebastian Hesselbarth
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=53AD7C24.5090408@gmail.com \
--to=sebastian.hesselbarth@gmail.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).