public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Kliment Yanev <Kliment.Yanev@helsinki.fi>, linux-kernel@vger.kernel.org
Subject: Re: Nokia c110 driver
Date: Tue, 9 Mar 2004 20:27:13 +0100	[thread overview]
Message-ID: <20040309192713.GA2182@mars.ravnborg.org> (raw)
In-Reply-To: <20040309080409.49fc0358.rddunlap@osdl.org>

On Tue, Mar 09, 2004 at 08:04:09AM -0800, Randy.Dunlap wrote:
> | 
> | 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.
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>

Maybe you can specify the .a file direct replacing the four .o file - 
should work but I have not tried.

> | | 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.
That patch was crap - the _shipped functionality covers this nicely.

> | | | 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
Should be:   nokia_c110-y := dllc.o dtools.o dhw.o dap.o dmgr.o dcfg.o
See also example above.

> | | | ~    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?
Looks OK except for the s/module/nokia_cs110/ point.

	Sam

  reply	other threads:[~2004-03-09 19:33 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 [this message]
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=20040309192713.GA2182@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=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