From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Question] bardrate both in gd_t and bd_t
Date: Fri, 04 Apr 2014 11:42:50 +0900 [thread overview]
Message-ID: <20140404114250.5C15.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <20140403215135.919D8383408@gemini.denx.de>
Hi Simon, Wolfgang,
On Thu, 03 Apr 2014 23:51:35 +0200
Wolfgang Denk <wd@denx.de> wrote:
> Dear Simon,
>
> In message <CAPnjgZ2PrHue3hTW__MaYBRMA3OFZ3p1k9D49rZatur9G5x--g@mail.gmail.com> you wrote:
> >
> > The duplication existed before generic board (i.e. each arch had its own
> > baudrate in global_data). I believe the reason for it being in bd_t is that
> > it can be passed to the kernel in that structure on some archs. So removing
> > it there may break some boards.
>
> Correct. In some (really old) kernel versions this was the way to pass
> this information to the kernel, so we neede dit there.
>
> > I suspect the reason it is in global_data is that the bd_t structure
> > doesn't exist until some time after the console is started up, so it
> > wouldn't be possible to do serial output otherwise.
>
> Also correct.
>
Thanks.
Sadly, it looks like we should keep both of the two.
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2014-04-04 2:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 7:12 [U-Boot] [Question] bardrate both in gd_t and bd_t Masahiro Yamada
2014-04-03 20:01 ` Tom Rini
2014-04-03 20:08 ` Simon Glass
2014-04-03 21:51 ` Wolfgang Denk
2014-04-04 2:42 ` Masahiro Yamada [this message]
2014-04-04 9:22 ` Wolfgang Denk
2014-04-04 11:19 ` Masahiro Yamada
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=20140404114250.5C15.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.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