public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Rafal Jaworowski <raj@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Pull request: u-boot-freebsd
Date: Thu, 27 Dec 2007 12:56:59 +0100	[thread overview]
Message-ID: <4773930B.9070903@semihalf.com> (raw)
In-Reply-To: <20071227000534.69AA024889@gemini.denx.de>

Dear Wolfgang,
you wrote:
> 
> I'm afraid I have to reject this pull request.
> 
> First, I think it breaks Linux booting support for a couple of boards
> (all 4xx ones, that is).
> 
>> The following changes since commit 41be969f4957115ed7b1fe8b890bfaee99d7a7a2:
>>   Wolfgang Denk (1):
>>         Release v1.3.1
>>
>> are available in the git repository at:
> ...
>>       [POWERPC] Simplify bd_info struct
> 
> This is the culprit.
> 
> With your  patch,  you  *always*  include  an  entry  "unsigned  long
> bi_bar;" in the bd_infor structure - even for processors which didn't
> have  one before (like 4xx boards). Thus you change the layout of the
> bd_info structure for such systems, which causes  an  incompatibility
> with the respective structure used by the Linux kernel.
> 
> Also, I have to admit that  I  dislike  this  type  of  #ifdef  based
> "simplification".  I  don't  think  the  resulting  code becomes more
> readable.
> 

Mhm, right. Maybe it was too much of an improvement :) Given all the legacy
dependencies between bd_info and Linux it's probably better to just leave it
as is and deal with those #idef'ed fields locally (where they are accessed).

> Please fix and resubmit.
> 

Will do.

> Then, we have this part:
> 
>>       [Net] Introduce standalone eth_receive() routine
> 
> This adds a lot of code to the networking code which is not neede dby
> most of the boards. Please make this an optional feature that get's
> only compiled in for boards that explicitely request it. Then run this
> patch separately through the network custodian.
> 

I already sent this patch to Ben and the list some time ago and got an initial
ACK, but I'll re-spin with.

kind regards,
Rafal

  reply	other threads:[~2007-12-27 11:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 12:06 [U-Boot-Users] Pull request: u-boot-freebsd Rafal Jaworowski
2007-12-17 12:39 ` Haavard Skinnemoen
2007-12-17 17:17   ` Rafal Jaworowski
2007-12-17 18:03     ` Haavard Skinnemoen
2007-12-18 22:40       ` Rafal Jaworowski
2007-12-18 23:08         ` Wolfgang Denk
2007-12-19  9:32         ` Haavard Skinnemoen
2007-12-17 18:06     ` Marcel Moolenaar
2007-12-17 18:19       ` Haavard Skinnemoen
2007-12-17 19:10         ` Marcel Moolenaar
2007-12-19  9:08           ` Haavard Skinnemoen
2007-12-18 23:00         ` Rafal Jaworowski
2007-12-19  9:15           ` Haavard Skinnemoen
2007-12-27  0:05 ` Wolfgang Denk
2007-12-27 11:56   ` Rafal Jaworowski [this message]
2007-12-27 16:27     ` Ben Warren
2007-12-27 17:19       ` Rafal Jaworowski
2007-12-27 17:06     ` Wolfgang Denk
2007-12-27 17:29       ` Rafal Jaworowski
2007-12-27 19:59         ` Ben Warren
2007-12-27 20:06         ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2008-02-21 11:06 Rafal Jaworowski
2008-02-22 12:01 ` Wolfgang Denk
2008-01-29 16:28 Rafal Jaworowski
2008-02-11 23:51 ` Wolfgang Denk
2008-01-09 19:04 Rafal Jaworowski
2008-01-09 22:08 ` Wolfgang Denk
2007-10-14 10:51 Rafal Jaworowski
2007-10-14 12:50 ` 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=4773930B.9070903@semihalf.com \
    --to=raj@semihalf.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