public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] include/ns16550.h: Unify structure declaration for	registers
Date: Mon, 27 Apr 2009 23:26:50 +0900	[thread overview]
Message-ID: <49F5C0AA.2000401@ruby.dti.ne.jp> (raw)
In-Reply-To: <m2ab62rz79.fsf@ohwell.denx.de>

Detlev Zundel wrote:
> To be honest, I did not expect such problems, as I saw no hints from
> comments on why this code was needed.  Thinking afresh, it now makes at
> least some sense why the code was.  It nevertheless was inconsistent, as
> the word access was only done in an asymmetric way regarding the
> REG_SIZES parameter.

I used to define locally "long + -16" variants.

>> How do I supposed to configure UART in my board config file?
> 
> I'm not sure at all.  I believe you tested with 4 and -4 and it doesn't
> work, right?

Right.

> Now we have the problem that we have byte registers (after all, there
> are only 8 bits significant even for your platform) which need to be
> accessed as 32-bit entities (or 16 bit for other platforms maybe).

This is why Linux 8250 driver supports not only UPIO_MEM but also
UPIO_MEM32.

> I don't see any way out here than to probably re-introduce different
> data-types again - which I certainly do not like too much as the
> registers stay 8 bit wide.

If there's no good alternatives, I think reverting is a good idea
because there must be other platforms affected by this change.

> Does anyone else have a good idea here?

Hm, how about introducing serial_{in,out} concepts from Linux?

  Shinya

  reply	other threads:[~2009-04-27 14:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 14:45 [U-Boot] [PATCH] include/ns16550.h: Unify structure declaration for registers Detlev Zundel
2009-04-03 14:55 ` Detlev Zundel
2009-04-03 23:24 ` Wolfgang Denk
2009-04-25  1:21 ` Shinya Kuribayashi
2009-04-27 13:41   ` Detlev Zundel
2009-04-27 14:26     ` Shinya Kuribayashi [this message]
2009-04-27 15:36       ` Detlev Zundel
2009-04-27 16:09         ` Detlev Zundel
2009-04-29 18:51         ` Shinya Kuribayashi
2009-04-29 19:12           ` Shinya Kuribayashi
2009-04-30 13:30             ` Detlev Zundel
2009-04-30 14:10               ` Detlev Zundel
2009-05-01  0:56               ` Shinya Kuribayashi
2009-05-01  5:29                 ` Shinya Kuribayashi
2009-04-30 12:26           ` Detlev Zundel
2009-04-30 12:52             ` Jerry Van Baren
2009-04-30 14:08               ` Detlev Zundel
2009-04-30 14:38                 ` Detlev Zundel
2009-04-30 17:06                 ` Jerry Van Baren
2009-05-01  2:21               ` Shinya Kuribayashi
2009-05-01  1:59             ` Shinya Kuribayashi
2009-05-04 15:40               ` Detlev Zundel
2009-05-04 21:21                 ` Scott Wood
2009-05-04 21:57                 ` Wolfgang Denk
2009-05-05  1:36                   ` Shinya Kuribayashi
2009-05-05  9:09                     ` Detlev Zundel

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=49F5C0AA.2000401@ruby.dti.ne.jp \
    --to=skuribay@ruby.dti.ne.jp \
    --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