mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Shaun Jackman" <sjackman@gmail.com>
To: "uClinux development list" <uClinux-dev@uclinux.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Nicolas Pitre" <nico@cam.org>
Subject: smc91x does not use netdev=
Date: Tue, 18 Jul 2006 16:06:52 -0600	[thread overview]
Message-ID: <7f45d9390607181506x177f1ff4r32daebd3070da01c@mail.gmail.com> (raw)

On 7/18/06, Shaun Jackman <sjackman@gmail.com> wrote:
> I've compiled the smc91x driver into my kernel (CONFIG_SMC91X=y), but
> the boot process complains `IP-Config: No network devices available.'
> I tried using the netdev kernel parameter to start the smc91x driver
> (netdev=1,0x300,eth0 and ether=1,0x300,eth0), but I don't see any
> output on the console from the smc91x driver. The driver doesn't
> appear to be starting. How do I start the smc91x driver? I'm compiling
> linux.2.6.14.7-hsc0 for ARM nommu (Atmel AT91).
>
> Thanks,
> Shaun

The smc91x driver doesn't seem to pull its parameters from the netdev=
parameter. Instead, a `platform_bus' is used, which requires a call to
`platform_add_devices' -- an example of this below. Could the smc91x
driver be modified to pulls its parameters from netdev=?

Cheers,
Shaun

#include <linux/device.h>

static struct resource smc91x_resources[] = {
	[0] = {
		.name	= "smc91x-regs",
		.start	= 0x300,
		.end	= 0x30f,
		.flags	= IORESOURCE_MEM,
	},
	[1] = {
		.start	= 17,
		.end	= 17,
		.flags	= IORESOURCE_IRQ,
	},
};

static struct platform_device smc91x_device = {
	.name		= "smc91x",
	.id		= -1,
	.num_resources	= ARRAY_SIZE(smc91x_resources),
	.resource	= smc91x_resources,
};

static struct platform_device *devices[] __initdata = {
	&smc91x_device,
};

void __init pathport_init(void)
{
	platform_add_devices(devices, ARRAY_SIZE(devices));
}

                 reply	other threads:[~2006-07-18 22:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7f45d9390607181506x177f1ff4r32daebd3070da01c@mail.gmail.com \
    --to=sjackman@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=uClinux-dev@uclinux.org \
    /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

all inboxes | Powered by JetHome®