[linux-cirrus] Re: Driver Changes
- From: Michael Burian <dynmail1@xxxxxxxxxxxxxxxxx>
- To: linux-cirrus@xxxxxxxxxxxxx
- Date: Mon, 22 Nov 2004 08:31:08 +0100
Manfred Gruber wrote:
>But i have a problem with that. On changing the ethernet driver i made a file
>ep93xx_eth_micro9_board.c/h. form the original ethernet driver.
>I see that the driver is compiled. o-file is there but it didn't get loaded.
>when i now configure original ethernet driver it gets loaded.
>
>
>
I don't know if you've got my last reply - but as you're reposting
the same question again I'll assume that you don't.
Please tell us if the stuff below fixes your problem or something
else is wrong.
Ethernet drivers need to get registered in "drivers/net/Space.c".
For the original ethernet driver this happens with
#ifdef CONFIG_EP93XX_ETHERNET
{ep93xx_probe, 0},
#endif
Looks like you've got to rename the ep93xx_probe function in your new
driver and add something like this to Space.c:
#ifdef CONFIG_EP93XX_ETHERNET_CUSTOM
{ep93xxcustom_probe, 0},
#endif
>Somewhere i have to change something for that problem but where ?
>Someone any idea.
>
>The same is with a new pull. There some things in fbmem and other files have
>changed. my custom framebuffer driver didn't get loaded. :-((
>
>
>
Best if you try to get the original fb driver to work first. It is
registered
in drivers/video/fbmem.c
#ifdef CONFIG_FB_EP93XX
{ "ep93xxfb", ep93xxfb_init, ep93xxfb_setup },
#endif
The above mentioned stuff also applies for the framebuffer.
rename the appropriate functions in your custom
driver and add something like this to drivers/video/fbmem.c
#ifdef CONFIG_FB_EP93XX_CUSTOM
{ "ep93xxfbcustom", ep93xxfbcustom_init, ep93xxfbcustom_setup },
#endif
Other related posts:
