linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Michael Guntsche <mike@it-loops.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: PHY not found after migration of gianfar driver to an of_platform_driver
Date: Tue, 3 Mar 2009 08:23:37 -0700	[thread overview]
Message-ID: <fa686aa40903030723p7d82edbfg5928adf9fe108b01@mail.gmail.com> (raw)
In-Reply-To: <a57485706bfc7aae2295acd743445312@localhost>

On Tue, Mar 3, 2009 at 2:49 AM, Michael Guntsche <mike@it-loops.com> wrote:
> On Tue, 03 Mar 2009 08:35:02 +0100, Michael Guntsche <mike@it-loops.com>
> wrote:
>> As for adding additional information to the tree, can I also use libfdt
>> functions in platform/83xx/rbppc.c or is it better to do this via a
>> dedicated platform_init that simpleboot then uses?

I'd do this in the bootwrapper.  I think it is easier to follow and
understand that way.

> Sorry, please forget this quesiton. Of course simpleboot only reads the
> embedded tree
> so if I change the tree there it is the same as changing the initial DTS
> file.
> I will try to boot with a standard vmlinux image and then add the values in
> rbppc.c.

Okay, that makes more sense.  So, now if you want a common wrapper
image to boot on all of the routerboard variants, then you need to
pull all the tricks you have out of your hat to figure out what board
it is running on so that the .dtb can be updated.  Is there an eeprom
or something on the board which might store serial numbers or MAC
addresses?

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2009-03-03 15:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 19:15 PHY not found after migration of gianfar driver to an of_platform_driver Michael Guntsche
2009-02-26 23:38 ` Michael Guntsche
2009-02-27 18:39   ` Michael Guntsche
2009-02-28 13:41     ` Michael Guntsche
2009-02-28 15:03 ` Grant Likely
     [not found]   ` <3B1D47A2-329E-491E-B3AC-E76C1CE1762D@it-loops.com>
     [not found]     ` <fa686aa40903011353t464b1df3obd553132e5bc2570@mail.gmail.com>
     [not found]       ` <CD026D29-687D-4078-960E-108CC94C30E4@it-loops.com>
2009-03-02  1:15         ` Grant Likely
2009-03-02 11:58           ` Michael Guntsche
2009-03-02 15:08             ` Grant Likely
2009-03-03  7:35               ` Michael Guntsche
2009-03-03  9:49                 ` Michael Guntsche
2009-03-03 15:23                   ` Grant Likely [this message]
     [not found]                     ` <7AC161D8-83A8-4330-A2CF-3120F15D9038@it-loops.com>
     [not found]                       ` <fa686aa40903031310o4e0c0b2bnba0544012b0fb8bc@mail.gmail.com>
     [not found]                         ` <68DDAAA9-42AF-4E9C-907C-7D3269816184@it-loops.com>
2009-03-04 15:57                           ` Grant Likely
2009-03-04 16:47                             ` Michael Guntsche
2009-03-05  7:41                             ` Michael Guntsche
2009-03-05 15:08                               ` Grant Likely
2009-03-08 12:18 ` Wolfgang Ocker

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=fa686aa40903030723p7d82edbfg5928adf9fe108b01@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mike@it-loops.com \
    /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;
as well as URLs for NNTP newsgroup(s).