From: Kliment Yanev <Kliment.Yanev@helsinki.fi>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Nokia c110 driver
Date: Wed, 10 Mar 2004 00:07:02 +0200 [thread overview]
Message-ID: <404E4006.5020604@helsinki.fi> (raw)
In-Reply-To: <20040309192713.GA2182@mars.ravnborg.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sam Ravnborg wrote:
|
| The above files are normal .o files, that should be linked in.
| So what you do is to rename the above files to:
| dhw.o_shipped
| dap.o_shipped
| dmgr.o_shipped
| dcfg.o_shipped
|
| And then in your makefile specify:
|
| obj-m := cs110.o
| cs110-y := dhw.o dap.o dmgr.o dcfg.o
| cs110-y += <additional .o files compield from .c files>
|
It compiled, finally. I have not been able to convince it to create a
device though, but the driver at least loads. Has anything changed in
the handling of netdevices between 2.4 and 2.6 that could cause this
behavior? That is, the pcmcia tools notice the card and load the module,
but then nothing else happens (module usecount 0, no netdevice present)
Is there some kbuild howto somewhere? If not, one is definitely
necessary I think. I had never heard about the _shipped thing (and I did
look around a bit and read and reread the driver porting guide chapter
on kbuild).
Now, is there anyone else that is in possession of this card and can
test the modified driver? I will try and make a patch tomorrow...a lot
of changes were needed and I think it's pretty messy (I am not an
experienced c person) but at least it compiles and loads now.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFATkAFrPQTyNB9u9YRAiNYAJ0XUOMwXrsdfUSwyXARUD0om7B4hQCfQO6N
a+0rrABQO8+/Sp1RWEfUIY4=
=vziv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-03-09 22:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 12:23 Nokia c110 driver Kliment Yanev
2004-02-28 18:41 ` Randy.Dunlap
2004-02-28 18:51 ` Kliment Yanev
2004-02-29 7:51 ` Kliment Yanev
2004-03-01 18:17 ` Randy.Dunlap
2004-03-08 14:59 ` Kliment Yanev
2004-03-08 17:06 ` Randy.Dunlap
2004-03-08 22:45 ` Kliment Yanev
2004-03-08 23:09 ` Randy.Dunlap
2004-03-08 23:22 ` Kliment Yanev
2004-03-08 23:36 ` Randy.Dunlap
2004-03-09 13:26 ` Kliment Yanev
2004-03-09 16:04 ` Randy.Dunlap
2004-03-09 19:27 ` Sam Ravnborg
2004-03-09 22:07 ` Kliment Yanev [this message]
2004-03-09 22:26 ` Sam Ravnborg
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=404E4006.5020604@helsinki.fi \
--to=kliment.yanev@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=sam@ravnborg.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