From: "Steven J. Hill" <sjhill@cotw.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: dwmw2@redhat.com, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org
Subject: Re: linux-2.4.6-pre8/drivers/mtd/nand/spia.c: undefined symbols
Date: Mon, 02 Jul 2001 07:38:59 -0500 [thread overview]
Message-ID: <3B406B63.4E28CA8A@cotw.com> (raw)
In-Reply-To: 200107012207.PAA01921@adam.yggdrasil.com
"Adam J. Richter" wrote:
>
> linux-2.4.6-pre8/drivers/mtd/nand/spia.c references four
> undefined symbols, presumably intended to be #define constants,
> although I am not sure what their values are supposed to be:
>
> IO_BASE
> FIO_BASE
> PEDR
> PEDDR
>
The way that I architected the raw NAND flash device driver was to
break it into 2 parts. 'nand.c' contains the actual driver code and
is considered to be device independent. 'spia.c' is the device
dependent part. You should write your own version of 'spia.c' and
"simply" fill in the addresses for the IO address and control
register address depending on your specific hardware. The above
symbols are only defined for my specific hardware. They should be
changed to values used on your hardware platform. Let me know if
you need further assistance.
-Steve
--
Steven J. Hill - Embedded SW Engineer
next parent reply other threads:[~2001-07-02 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200107012207.PAA01921@adam.yggdrasil.com>
2001-07-02 12:38 ` Steven J. Hill [this message]
2001-07-02 12:52 ` linux-2.4.6-pre8/drivers/mtd/nand/spia.c: undefined symbols Alan Cox
2001-07-02 13:14 ` David Woodhouse
2001-07-03 17:57 ` Steven J. Hill
2001-07-02 12:53 ` David Woodhouse
2001-07-03 13:10 Adam J. Richter
2001-07-03 15:35 ` Steven J. Hill
-- strict thread matches above, loose matches on Subject: below --
2001-07-03 15:53 Adam J. Richter
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=3B406B63.4E28CA8A@cotw.com \
--to=sjhill@cotw.com \
--cc=adam@yggdrasil.com \
--cc=dwmw2@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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