public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kliment Yanev <Kliment.Yanev@helsinki.fi>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Nokia c110 driver
Date: Tue, 09 Mar 2004 15:26:58 +0200	[thread overview]
Message-ID: <404DC622.7020300@helsinki.fi> (raw)
In-Reply-To: <20040308153602.331f079e.rddunlap@osdl.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Randy.Dunlap wrote:
|
| I looked there but didn't see such symbols (using 'nm').
| What did you use to see them?
| The strings that I see all seem to contain 16-bit characters.

dhw.o, dap.o, dmgr.o and dcfg.o are located in nokia_cs.a, which does
not include source. These are the parts that actually access the card
and configure frequencies etc. They don't seem to be linked, since the
dhw_* symbols are unknown in the module. Manually linking them with the
.ko prevents it from being loaded (or maybe I am linking them wrong).
They are defined in corresponding .h files mostly. I think that should
handle all of them. nm sees the symbols in those .o files and in
nokia_cs.a where they came from, but I haven't checked if all of them
are there (I will do so soon). Note that nokia_cs.a is in the binary
package where the firmware is. It is not the same as the firmware file
(smac*.bin).

I am not at all familiar with kbuild (other than the driver porting
howto) and actually have not even written c code before attempting this
driver. Can you advise me on how to link external files like this into a
.ko without breaking the module?


|
|
| | | You know, it's possible that you could purchase a card that already
| | | works on Linux 2.6.... that might be a better solution than trying
| | | to use an unknown binary module.
|
| Well, Sam Ravnborg did post a patch in the last week or so that
| should help with (some) binary files...  probably .o and not .bin,
| or maybe it doesn't matter.
|

Clarify please. A patch to kbuild? Or to the kernel? Note that the .bin
file is only the card firmware. No point looking in that for anything.
The binary part of the _driver_ is in nokia_cs.a, which contains .o files.

|
| | At this point I am doing this just to see if it will work... I don't
| | need the card for another week or so and if I don't get this one to work
| | I'll just buy another one. Yet I have the feeling that this card will
| | work before long... if only I could get those files linked that is...
| |
| | My makefile (dhw, dap, dmgr and dcfg are in the binary parts, present in
| | the current dir as dhw.o etc.; all the others are .c files that get
| | compiled during a make):
| |
| | ~    ifneq ($(KERNELRELEASE),)
| | ~    obj-m       := nokia_c110.o
| | ~    module-objs := dllc.o dtools.o dhw.o dap.o dmgr.o dcfg.o
| |
| | ~    else
| | ~    KDIR        := /lib/modules/$(shell uname -r)/build
| | ~    PWD         := $(shell pwd)
| |
| | ~    default:
| | ~        $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
| | ~    endif

Can you tell me if the makefile is correct?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFATcYhrPQTyNB9u9YRAmHAAKCgpcd4WMfVsO7VAIhrQruuYdBKSgCfY72J
f6HeLO79lWj3S+bZcuqYiOQ=
=6UIa
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-03-09 13:26 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 [this message]
2004-03-09 16:04                     ` Randy.Dunlap
2004-03-09 19:27                       ` Sam Ravnborg
2004-03-09 22:07                         ` Kliment Yanev
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=404DC622.7020300@helsinki.fi \
    --to=kliment.yanev@helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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