On Thu, 2009-02-26 at 20:15 +0100, Michael Guntsche wrote:
For testing purposes I tried a recent git snapshot and noticed
that the gianfar driver had problems.
While the the Gianfar was detected
[...]
trying to up either of the devices gave me
[8.724818] m...@24520:01 not found
[
On Thu, Mar 5, 2009 at 12:41 AM, Michael Guntsche m...@it-loops.com wrote:
On Wed, 4 Mar 2009 08:57:59 -0700, Grant Likely grant.lik...@secretlab.ca
wrote:
You might be able to use of_attach_node() prom_add_property() to
modify the tree, but I've never done it myself. Give it a try and
tell
I'm posting this back on the mailing list. You're not being dense and
there are good questions here which others might elaborate more on.
On Tue, Mar 3, 2009 at 2:56 PM, Michael Guntsche m...@it-loops.com wrote:
The routeboard is already providing a device-tree albeit not a very good
one,
On Mar 4, 2009, at 16:57, Grant Likely wrote:
I need more information here. What do you mean when you say plain
kernel. What file from the build process do you use, and how do you
boot it?
I build the kernel with
make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- vmlinux
I take the
On Wed, 4 Mar 2009 08:57:59 -0700, Grant Likely grant.lik...@secretlab.ca
wrote:
You might be able to use of_attach_node() prom_add_property() to
modify the tree, but I've never done it myself. Give it a try and
tell me if it works. :-)
Hello Grant,
I made some progress in this area, but
On Tue, 03 Mar 2009 08:35:02 +0100, Michael Guntsche m...@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?
Sorry, please forget this
On Tue, Mar 3, 2009 at 2:49 AM, Michael Guntsche m...@it-loops.com wrote:
On Tue, 03 Mar 2009 08:35:02 +0100, Michael Guntsche m...@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
On Sun, 1 Mar 2009 18:15:32 -0700, Grant Likely grant.lik...@secretlab.ca
wrote:
So, what you need is a new adapter which parses the data passed in by
routerboot (maybe call it routerImage?) and modifies the .dtb blob to
match. You can use simpleImage as a starting point.
I had a look at
On Mon, Mar 2, 2009 at 4:58 AM, Michael Guntsche m...@it-loops.com wrote:
On Sun, 1 Mar 2009 18:15:32 -0700, Grant Likely grant.lik...@secretlab.ca
wrote:
So, what you need is a new adapter which parses the data passed in by
routerboot (maybe call it routerImage?) and modifies the .dtb blob
On Mon, 2 Mar 2009 08:08:02 -0700, Grant Likely grant.lik...@secretlab.ca
wrote:
On Mon, Mar 2, 2009 at 4:58 AM, Michael Guntsche m...@it-loops.com
wrote:
You mean like loading it of the CF or something? Yeah, I suppose so
if you wrote a minimal CF driver, but that seems the hard way around
[moving this conversation back to the mailing list. Don't forget to
use 'reply-all' on mailing list conversations.]
On Sun, Mar 1, 2009 at 4:49 PM, Michael Guntsche m...@it-loops.com wrote:
On Mar 1, 2009, at 22:53, Grant Likely wrote:
On Sun, Mar 1, 2009 at 1:04 PM, Michael Guntsche
Hello list,
Just a little update and one question.
I spent this night to create a DTS file for the board. I took the
output of the existing /proc/device-tree as basis and added
information regarding the TBI's.
Then I created a simpleImage.
/dts-v1/;
/ {
linux,phandle = 0x100;
Hey Michael,
I just wanted to let you know that I'm reading your questions, and I'm
crafting a reply, but it's not trivial and I'm also swamped under at
the moment. I should have something for you in the next few days. I
just didn't want you to think you were being ignored.
g.
On Thu, Feb 26,
Ok, I made some progress but still no fix for it.
The code fails in bus_find_device
if (match(dev, data)
returns false. Data in this case is m...@24520.00 or .01 depending on
the nic but the only mdio device that exists is m...@24520.1f which is
not the phy.
If I boot with 2.6.28.3 I see
Hello everyone,
I recently obtained a Mikrotik RB600 and applied the patch from http://cynigram.com/~nfontes/rb600/
to get it up and running with 2.6.28.3
With this patch applied everything was detected on the board and
worked. For testing purposes I tried a recent git snapshot and noticed
Some more information regarding this board. This is the output of
dtc /proc/device/ree:
I removed all information not relevant to networking
/dts-v1/;
/ {
linux,phandle = 0x100;
#size-cells = 0x1;
#address-cells = 0x1;
compatible = MPC83xx;
model =
16 matches
Mail list logo
