All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3: Print correct silicon revision
Date: Wed, 22 Apr 2009 17:40:54 +0200	[thread overview]
Message-ID: <49EF3A86.10707@googlemail.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301D6F6E4D0@dbde02.ent.ti.com>

Premi, Sanjeev wrote:
>> -----Original Message-----
>> From: Dirk Behme [mailto:dirk.behme at googlemail.com] 
>> Sent: Wednesday, April 22, 2009 1:04 AM
>> To: Premi, Sanjeev
>> Cc: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] [PATCH] OMAP3: Print correct silicon revision
>>
>> Dear Premi,
>>
>> Premi, Sanjeev wrote:
>>>> -----Original Message-----
>>>> From: Premi, Sanjeev 
>>>> Sent: Tuesday, April 21, 2009 11:37 PM
>>>> To: 'Dirk Behme'
>>>> Cc: u-boot at lists.denx.de
>>>> Subject: RE: [U-Boot] [PATCH] OMAP3: Print correct silicon revision
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Dirk Behme [mailto:dirk.behme at googlemail.com] 
>>>>> Sent: Tuesday, April 21, 2009 10:26 PM
>>>>> To: Premi, Sanjeev
>>>>> Cc: u-boot at lists.denx.de
>>>>> Subject: Re: [U-Boot] [PATCH] OMAP3: Print correct 
>> silicon revision
>>>>> Dear Premi,
>>>>>
>>>>> Sanjeev Premi wrote:
>>>>>> The function display_board_info() displays the silicon
>>>>>> revision as 2 - based on the return value from get_cpu_rev().
>>>>>>
>>>>>> This is incorrect as the current Si version is 3.1
>>>>> Thanks for the patch and fixing this!
>>>>>
>>>>>> This patch displays the correct version; but does not
>>>>>> change get_cpu_rev() to minimize the code impact.
>>>>> I wonder if it wouldn't be better (and cleaner) to fix 
>>>> get_cpu_rev()?
>>>>
>>>> Yes. This is what I started with; but then this is where I 
>> felt that
>>>> fix may run 'deeper"
>>>>
>>>> u32 get_board_type(void)
>>>> {
>>>> 	if (get_cpu_rev() == CPU_3430_ES2)
>>>> 		return sysinfo.board_type_v2;
>>>> 	else
>>>> 		return sysinfo.board_type_v1;
>>>> }
>>>>
>>> ...sorry, mail 'went' before I wanted to!
>>>
>>>> I couldn't figure out how this impacts boards other than the EVM.
>>> Though I admit not having much time looking for the impact. Beyond
>>> this, I believe the fix could be straight forward.
>> What's about something like in the attachment? Compile tested 
>> only. Do 
>> you like to test it?
> 
> Yes, this works on the EVM.

Great, thanks for testing!

> I did spend some more time & fouund that value from get_board_type is
> ignored in the display_board_info().

Hmm, yes, good catch.

> I will submit a patch to remove this function if it is really not needed.

Ok.

Best regards

Dirk

Btw.: Updated patch in attachment, maybe it helps you. Tested on Beagle.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: omap3_revision.txt
Url: http://lists.denx.de/pipermail/u-boot/attachments/20090422/34f85878/attachment-0001.txt 

  reply	other threads:[~2009-04-22 15:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 16:23 [U-Boot] [PATCH] OMAP3: Print correct silicon revision Sanjeev Premi
2009-04-21 16:55 ` Dirk Behme
2009-04-21 18:06   ` Premi, Sanjeev
2009-04-21 18:33     ` Dirk Behme
2009-04-21 18:25   ` Premi, Sanjeev
2009-04-21 19:34     ` Dirk Behme
2009-04-21 19:38       ` Premi, Sanjeev
2009-04-22 11:40       ` Premi, Sanjeev
2009-04-22 15:40         ` Dirk Behme [this message]
2009-04-22 21:20 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-23 14:45   ` Dirk Behme

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=49EF3A86.10707@googlemail.com \
    --to=dirk.behme@googlemail.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 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.