From: Sinan Akman <sinan@writeme.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] configs: ls1021atwr: Enable ID EEPROM for SD boot
Date: Mon, 19 Oct 2015 07:14:08 -0400 [thread overview]
Message-ID: <5624D080.9080009@writeme.com> (raw)
In-Reply-To: <BLUPR03MB1345C59E5F5FDA9EC1B8278833A0@BLUPR03MB134.namprd03.prod.outlook.com>
Hi Yuan
On 19/10/15 05:21 AM, Yao Yuan wrote:
> Hi Sinan Akman,
>
> Yes, I mean the Rev 1.0 silicon.
> Sorry, I can't guarantee that there aren't any boards with Rev1.0 silicon are in user's hands.
> Because we have also delivery very little board with Rev1.0 silicon to customer or developer for developing, assessing and verifying in the early stages.
Thanks for the follow up on this, but I don't think that there were only
very few rev1.0 boards delivered. These were the boards bought from
distributor and during the time span of many weeks.
I don't know the details and the impact of this patch exactly but
if the patch will break any rev1.0 board I don't think this would be
acceptable. There are definitely enough number of rev1.0 boards
made generally available (not specifically for early adapters etc)
that we should not break u-boot running on them.
> Also we haven't support Rev1.0 in our SDK now.
Sorry, but this is a bit irrelevant here. I'd expect u-boot mainline
does not necessarily follow what your SDK stops supporting. If
u-boot supported rev1.0 boards and if there are still many of
them out there I see no reason to break this.
Regards
Sinan Akman
>
> Thanks.
>
> Best Regards,
> Yuan Yao
>
>> -----Original Message-----
>> From: Sinan Akman [mailto:sinan at writeme.com]
>> Sent: Friday, October 16, 2015 3:37 AM
>> To: Sun York-R58495 <yorksun@freescale.com>; Yuan Yao-B46683
>> <yao.yuan@freescale.com>; Wang Huan-B18965 <alison.wang@freescale.com>
>> Cc: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] [PATCH] configs: ls1021atwr: Enable ID EEPROM for SD
>> boot
>>
>>
>> Hi Yuan
>>
>> On 15/10/15 12:40 PM, York Sun wrote:
>>>
>>> On 10/15/2015 12:55 AM, Yuan Yao-B46683 wrote:
>>>> Hi york,
>>>>
>>>> The earlier SoC is just LS1021a rev1.0, but rev1.0 haven't delivery to the
>> customer.
>>>> Also the rev1.0 has since gone out of production.
>>>> So we don't have necessary to support rev1.0 because no one will or
>> possibly to use rev1.0.
>>
>> Just to make this clear, the boards we bought all show :
>>
>> CPU: Freescale LayerScape LS1021E, Version: 1.0, (0x87081110)
>>
>> When you mention "rev1.0 haven't delivery to the customer" are you not
>> referring to Rev 1.0 silicon ?
>>
>> Regards
>> Sinan Akman
>>
>>> OK.
>>>
>>> York
>>> _______________________________________________
>>> U-Boot mailing list
>>> U-Boot at lists.denx.de
>>> http://lists.denx.de/mailman/listinfo/u-boot
>>>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
next prev parent reply other threads:[~2015-10-19 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 7:48 [U-Boot] [PATCH] configs: ls1021atwr: Enable ID EEPROM for SD boot Yuan Yao
2015-10-14 21:21 ` York Sun
2015-10-15 7:55 ` Yao Yuan
2015-10-15 16:40 ` York Sun
2015-10-15 19:37 ` Sinan Akman
2015-10-19 9:21 ` Yao Yuan
2015-10-19 11:14 ` Sinan Akman [this message]
2015-10-19 15:02 ` York Sun
2015-10-21 3:59 ` Yao Yuan
2015-10-21 5:37 ` York Sun
2015-10-30 16:21 ` York Sun
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=5624D080.9080009@writeme.com \
--to=sinan@writeme.com \
--cc=u-boot@lists.denx.de \
/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