All of lore.kernel.org
 help / color / mirror / Atom feed
From: Remco Poelstra <remco.poelstra@duran-audio.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Cleaning up new port
Date: Tue, 17 Mar 2009 13:59:17 +0100	[thread overview]
Message-ID: <49BF9EA5.5040805@duran-audio.com> (raw)
In-Reply-To: <20090317121419.DD438832E8B7@gemini.denx.de>

Wolfgang Denk schreef:
> In message <49BF91D5.2030602@duran-audio.com> you wrote:
>> I've finished my port of U-boot 2008.10 to the LPC2468. I've based my 
>> port on code by Embedded Artists, which was based on U-boot 1.1.6.
>> The LPC2468 is an ARM processor with build in peripherals, so I need to 
>> divide my code into LPC2468 generic part and a part for my board only 
>> (which is not to be published). I have however no clue on how to do 
> 
> Not pubslishing your code would be a stupid thing to do. Are you aware
> how quickly out-of-mainline code rots? You are already two releases
> behind against current mainline, and a lot of changes have already
> been queued up in the "next" branch for the next release. 

I fully understand. The problem is that there is a special Ethernet PHY 
on the board which is under a NDA, so I cannot publish code surrounding 
it. I can publish the general part of the ethernet driver.

> Try to forward port your stuff to the "next" branch (you will have to
> do that to submit any patches), and then think again if it makes sense
> for you to maintain an out-of-tree port.  It doesn't.
> 
>> that. What code should belong where?
>> Is there any documentation on the exact code structure of U-boot? Is 
>> anyone here interested in LPC2468 support and willing to offer some help?
> 
> Apply common sense. Then submit your patches. We  will  tell  you  if
> they  fit.  Note  that  so  far there is no LPC2468 support in U-Boot
> mainline, so you must provide some complete working  board  port,  or
> there would be code which cannot even be compiled, and we don't allow
> that.

I see, I will provide a working example.

Regards,

Remco Poelstra

  reply	other threads:[~2009-03-17 12:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 12:04 [U-Boot] Cleaning up new port Remco Poelstra
2009-03-17 12:14 ` Wolfgang Denk
2009-03-17 12:59   ` Remco Poelstra [this message]
2009-03-17 13:09     ` Wolfgang Denk
2009-03-17 13:49       ` Jerry Van Baren

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=49BF9EA5.5040805@duran-audio.com \
    --to=remco.poelstra@duran-audio.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.