public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3: Update Overo and Beagle environment
Date: Sun, 27 Sep 2009 06:52:24 -0500	[thread overview]
Message-ID: <4ABF51F8.9040009@windriver.com> (raw)
In-Reply-To: <5e088bd90909260641q6b5a3b03j9492c0c0f7f73c1b@mail.gmail.com>

Steve Sakoman wrote:
> On Fri, Sep 25, 2009 at 1:47 PM, Tom <Tom.Rix@windriver.com> wrote:
>> Dirk Behme wrote:
>>> From: Steve Sakoman <sakoman@gmail.com>
>>>
>>> Update default environment to support new kernel DSS2 subsystem and
>>> simplify rootfs type and location changes.
>>>
>>> Signed-off-by: Steve Sakoman <sakoman@gmail.com>
>>> Signed-off-by: Dirk Behme <dirk.behme@googlemail.com>
>>>
>>> ---
>>>  include/configs/omap3_beagle.h |   27 +++++++++++++++++++--------
>>>  include/configs/omap3_overo.h  |   27 +++++++++++++++++++--------
>>>  2 files changed, 38 insertions(+), 16 deletions(-)
>>>
>>> Index: u-boot-ti/include/configs/omap3_overo.h
>>> ===================================================================
>>> --- u-boot-ti.orig/include/configs/omap3_overo.h
>>> +++ u-boot-ti/include/configs/omap3_overo.h
>>> @@ -155,16 +155,27 @@
>>>  #define CONFIG_EXTRA_ENV_SETTINGS \
>>>       "loadaddr=0x82000000\0" \
>>>       "console=ttyS2,115200n8\0" \
>>> -     "videomode=1024x768 at 60,vxres=1024,vyres=768\0" \
>>> -     "videospec=omapfb:vram:2M,vram:4M\0" \
>>> +     "vram=12M\0" \
>>> +     "dvimode=1024x768MR-16 at 60\0" \
>>> +     "defaultdisplay=dvi\0" \
>>> +     "mmcroot=/dev/mmcblk0p2 rw\0" \
>>> +     "mmcrootfstype=ext3 rootwait\0" \
>>> +     "nandroot=/dev/mtdblock4 rw\0" \
>>> +     "nandrootfstype=jffs2\0" \
>>>       "mmcargs=setenv bootargs console=${console} " \
>>> -             "video=${videospec},mode:${videomode} " \
>>> -             "root=/dev/mmcblk0p2 rw " \
>>> -             "rootfstype=ext3 rootwait\0" \
>>> +             "vram=${vram} " \
>>> +             "omapfb.mode=dvi:${dvimode} " \
>>> +             "omapfb.debug=y " \
>> Is setting the debug option needed ?
>> This would seem useful (from the name) only to developers
> 
> DSS2 is still under active development.  This setting makes user
> support easier since boot logs contain needed debug info.
> 

Or it turns them all into beta-testers.
It is a toss up if this is a good thing
I will go with it.
OK.

>>> +             "omapdss.def_disp=${defaultdisplay} " \
>>> +             "root=${mmcroot} " \
>>> +             "rootfstype=${mmcrootfstype}\0" \
>>>       "nandargs=setenv bootargs console=${console} " \
>>> -             "video=${videospec},mode:${videomode} " \
>>> -             "root=/dev/mtdblock4 rw " \
>>> -             "rootfstype=jffs2\0" \
>>> +             "vram=${vram} " \
>>> +             "omapfb.mode=dvi:${dvimode} " \
>>> +             "omapfb.debug=y " \
>>> +             "omapdss.def_disp=${defaultdisplay} " \
>>  From vram to omapdss.def_disp are common for nand and mmc.
>> These should be changed to something like
>>
>> "videoargs= .... "
>>
>> Similar for beagle.
> 
> I'm not sure exactly what you are suggesting.  The current setup is
> tailored to make user support easier.
> 
> If someone wants to use the 4.3" LCD display option, you tell them to
> simply type:
> 
> setenv defaultdisplay=lcd43
> saveenv
> 
Yes I see how just a single video_args= would not give you this flexiblity.
A lesser way to do this would be to that you may want to do is
video_args="${defaultdisplay} ${dvimode}  ..  "

Tom

  reply	other threads:[~2009-09-27 11:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-25 18:49 [U-Boot] [PATCH] OMAP3: Update Overo and Beagle environment Dirk Behme
2009-09-25 20:47 ` Tom
2009-09-26  5:20   ` Dirk Behme
2009-09-26 13:41   ` Steve Sakoman
2009-09-27 11:52     ` Tom [this message]
2009-09-27 14:02       ` Steve Sakoman
2009-09-27 14:21         ` Tom
2009-10-10 18:03           ` Steve Sakoman
2009-10-10 18:13             ` Dirk Behme
2009-10-10 18:32               ` Paulraj, Sandeep

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=4ABF51F8.9040009@windriver.com \
    --to=tom.rix@windriver.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