public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mirek23 <miroslaw.dach@psi.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] uImage starting problem on Virtex-4 (PPC405)
Date: Tue, 4 Sep 2007 05:50:40 -0700 (PDT)	[thread overview]
Message-ID: <12477610.post@talk.nabble.com> (raw)
In-Reply-To: <fa686aa40708310817h736fa618r360a7ec26594ed04@mail.gmail.com>


Hi Grant,

As regards the board info I have verified that board info structure is the
same in kernel 2.6.21 and kernel2.4:

typedef struct board_info {
        unsigned int bi_memsize;        /* DRAM installed, in bytes */
        unsigned char bi_enetaddr[6];   /* Local Ethernet MAC address */
        unsigned int bi_intfreq;        /* Processor speed, in Hz */
        unsigned int bi_busfreq;        /* Bus speed, in Hz */
        unsigned int bi_pci_busfreq;    /* PCI Bus speed, in Hz */
} bd_t;

The location of that structure is only different. In the kernel 2.6.21 is
located in :
./arch/ppc/platforms/4xx/virtex.h
and in the kernel 2.4:
./arch/ppc/platforms/xilinx_ml*.h 

Could you please confirm if the board info you mentioned in your last post
is the structure listed above or something else? I am just trying to sort
out the problem with booting my kernel from u-boot and still no success.

Best Regards

Mirek


Grant Likely-2 wrote:
> 
> On 8/31/07, Miroslaw Dach <miroslaw.dach@psi.ch> wrote:
>> Hi Grant,
>>
>>         What would you suggest me to do ?
>>
>> > I just thought of something.  You're using kernel v. 2.6.21-rc6.
>> > However, it wasn't until 2.6.22 that the kernel tree was updated to
>> > use the same board info structure as u-boot.  (specifically commit
>> > 9be4dcb606e647854760fafd0bb1cb3e1a804d16)
>> >
>> > You probably have a u-boot/kernel board info mismatch.
>>
>> What would you suggest me to do ?
>> How to sort out this problem?
> 
> Upgrade your kernel (preferred) or backport the changes to your kernel
> (not recommended)
> 
> g.
> 
> -- 
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> grant.likely at secretlab.ca
> (403) 399-0195
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
> 
> 

-- 
View this message in context: http://www.nabble.com/uImage-starting-problem-on-Virtex-4-%28PPC405%29-tf4360138.html#a12477610
Sent from the Uboot - Users mailing list archive at Nabble.com.

  parent reply	other threads:[~2007-09-04 12:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 13:21 [U-Boot-Users] uImage starting problem on Virtex-4 (PPC405) Miroslaw Dach
2007-08-31 14:43 ` Grant Likely
2007-08-31 15:15   ` Miroslaw Dach
2007-08-31 15:17     ` Grant Likely
2007-08-31 15:34       ` Miroslaw Dach
2007-09-04 12:50       ` Mirek23 [this message]
2007-09-04 13:36         ` Grant Likely
2007-09-05 10:41           ` Mirek23

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=12477610.post@talk.nabble.com \
    --to=miroslaw.dach@psi.ch \
    --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