public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Added support for multiple serial for MPC8XX
Date: Wed, 6 Jun 2007 07:08:26 +0200	[thread overview]
Message-ID: <200706060708.26380.sr@denx.de> (raw)
In-Reply-To: <20070605234949.F2E1B353A05@atlas.denx.de>

Hi Stefano,

On Wednesday 06 June 2007, Wolfgang Denk wrote:
> > However, I didn't want to have two different coding styles with different
> > meaning inside the same file. In fact, some lines later the whole mess of
> > #ifdef was already inserted for the ppc4xx architecture using
> > CONFIG_CONS_INDEX to switch among the interfaces.
>
> Please feel free to clean this up the same was as I suggested. I'm
> sure Stefan Roese will ACK such a change.
>
> We should get rid of all this CONFIG_CONS_INDEX stuff.

Yes, please. I'll be happy to test on 4xx hardware, if you have a patch 
removing this maze. Thanks.

> > I didn't want to change this part because this would break all ppc4xx
> > boards that are not part of the U-Boot tree. So I preferred to add a lot
> > of #ifdef using the same CONFIG defines as in ppc4xx instead of creating
> > a new one.
>
> I'm afraid I don't understand what you mean. Usually  we  don't  care
> about boards that are not part of the U-Boot tree.

Right. It's impossible to support the non official board ports. Sometimes we 
have to make changes that *can* break inofficial code.

> > I will resend the patch with the modifications for the mpc8xx, without
> > touching ppc4xx part. This would not break any custom board.
>
> Please feel free to fix it for the existing 4xx boards as well. I'd
> really appreciate this, and I even volunteer to test it on a few of
> them.

No need to. I'll do it.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2007-06-06  5:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 12:47 [U-Boot-Users] [PATCH] Added support for multiple serial for MPC8XX Stefano Babic
2007-06-05 13:53 ` Wolfgang Denk
2007-06-05 19:39   ` Stefano Babic
2007-06-05 23:49     ` Wolfgang Denk
2007-06-06  5:08       ` Stefan Roese [this message]
2007-06-06 13:03       ` Stefano Babic
2007-06-06 13:13         ` Stefan Roese
2007-06-06 13:27           ` Stefano Babic
2007-06-06 13:55         ` Wolfgang Denk
2007-06-06 14:20           ` Stefano Babic
2007-06-06 21:35           ` [U-Boot-Users] [PATCH] Added support for multiple serial for MPC8XX (resubmit) Stefano Babic
2007-06-15 16:03             ` Detlev Zundel
2007-06-15 19:38               ` Wolfgang Grandegger
2007-06-17 13:31                 ` Stefano Babic
2007-06-17 21:16                   ` Wolfgang Denk
2007-06-18  5:18                   ` Wolfgang Grandegger
2007-06-17 11:35               ` Stefano Babic
  -- strict thread matches above, loose matches on Subject: below --
2007-06-05 13:56 [U-Boot-Users] [PATCH] Added support for multiple serial for MPC8XX Wolfgang Denk

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=200706060708.26380.sr@denx.de \
    --to=sr@denx.de \
    --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