mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: How to handle more than one network device in barebox
Date: Thu, 17 Feb 2011 12:24:14 +0100	[thread overview]
Message-ID: <20110217112414.GC24426@pengutronix.de> (raw)
In-Reply-To: <201102171157.14757.jbe@pengutronix.de>

On Thu, Feb 17, 2011 at 11:57:14AM +0100, Juergen Beisert wrote:
> Hi,
> 
> due to the fact (all?) network device drivers in barebox are using xzalloc to 
> allocate their "struct eth_device" the embedded "struct dev's" '.id' is 
> always '0'. So the registration of a second network device fails always with
> 
>  register_device: already registered eth0
> 
> Currently there is no way to overwrite the network device's ID. If I init 
> the "edev->dev.id" with '-1', it works. But it would be nice to define the 
> network device ordering from inside the platform (and not only with the order 
> I register the base devices). And copying the ".id" from the registered base 
> device also does not work if the network devices are of different type, due 
> to the framework starts with index 0 for different names.
> 
> Any ideas how to?

I stumbled upon this aswell.

I solved this with the following patch which I forgot to send to the
list. It still does not solve the issue that the order of network
devices is defined by the registration order, but at least it makes
multiple network devices work again.

Sascha

commit fe1864bdcf237a3ed0f5391e1cbd6cec13b518bc
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date:   Thu Feb 3 13:07:57 2011 +0100

    network: initialize new net device id with -1
    
    Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

diff --git a/net/eth.c b/net/eth.c
index 8333d80..9eae17c 100644
--- a/net/eth.c
+++ b/net/eth.c
@@ -151,6 +151,7 @@ int eth_register(struct eth_device *edev)
 	}
 
 	strcpy(edev->dev.name, "eth");
+	edev->dev.id = -1;
 	register_device(&edev->dev);
 
 	dev->type_data = edev;

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2011-02-17 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 10:57 Juergen Beisert
2011-02-17 11:24 ` Sascha Hauer [this message]

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=20110217112414.GC24426@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=jbe@pengutronix.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