public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Status LEDs status?
Date: Mon, 09 Jun 2003 15:18:36 +0300	[thread overview]
Message-ID: <3EE47B1C.3090601@intracom.gr> (raw)
In-Reply-To: <20030609115441.A7399C5FD7@atlas.denx.de>

Wolfgang Denk wrote:

>In message <3EE46FBE.3020803@intracom.gr> you wrote:
>  
>
>>Well the first thing we can do is removing
>>the redundant code.
>>
>>With the following patch I moved the status LED code
>>from the cpu directories and placed it in the drivers
>>directory.
>>
>>The code for mpc8xx is the superset of both
>>the 8260 and 5xx code, so this is the base for it.
>>
>>Patch applies cleanly againt CVS and is tested to
>>build in 8xx/8260/5xx configs that use LEDs.
>>
>>What do you think?
>>    
>>
>
>This is exactly what I do NOT want.
>
>I do not want tosee processor specific code  in  common  directories.
>The  drivers/ directory is intended for general code that applies for
>all CPUs.
>
>Best regards,
>
>Wolfgang Denk
>
>
Whoa, hold on.

First of all when you have three copies of the the same thing in different
directories there's bound to be trouble.
For example the 8260 & 5xx copies are already slightly out of sync.

Secondly LEDs are board specific and not cpu specific.
It was a coincidence that up to now the LEDs happened to be in cpu ports
and could be groupped under the cpu directories.

I think it is trivial to abstract the led operations into their respective
cpu include files for the common case. The existing board config headers
shouldn't be modified, while allowing other boards to override them.

In this case the status led code would be generic for all configurations
that support them.

Regards

Pantelis

  reply	other threads:[~2003-06-09 12:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09  9:26 [U-Boot-Users] Status LEDs status? Pantelis Antoniou
2003-06-09 10:07 ` Wolfgang Denk
2003-06-09 11:30   ` Pantelis Antoniou
2003-06-09 11:54     ` Wolfgang Denk
2003-06-09 12:18       ` Pantelis Antoniou [this message]
2003-06-09 20:49         ` Wolfgang Denk
2003-06-10  6:48           ` Pantelis Antoniou
2003-06-19 18:42             ` Wolfgang Denk
2003-06-10  6:49           ` Pantelis Antoniou

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=3EE47B1C.3090601@intracom.gr \
    --to=panto@intracom.gr \
    --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