From: Pierre AUBERT <p.aubert@staubli.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] FDC patch
Date: Tue, 05 Nov 2002 17:57:59 +0100 [thread overview]
Message-ID: <3DC7F897.FA17CA3D@staubli.com> (raw)
Hello,
The attached patch modify the fdcboot source code to support wide
hardware designs
I needed to add some defines because :
- on some boards, the fdc registers aren't contiguous (for example they
can be aligned on a 32 bits boundary).
- the fdc chipset has a 8 bits data bus. Then, it can be connected on
the processor data bus on D0-D7 or D8-D15 or D16-D23 or D24-D31.
- the floppy drive can be on drive other than 0.
- some chipsets need extra initializations.
CFG_ISA_IO_STRIDE : defines the spacing between fdc chipset registers
(default value 1)
CFG_ISA_IO_OFFSET : defines the offset of register from address. It
depends on which part of the data bus is connected to the fdc chipset.
(default value 0)
CFG_FDC_DRIVE_NUMBER : the default drive number (default value 0)
If CFG_ISA_IO_STRIDE CFG_ISA_IO_OFFSET and CFG_FDC_DRIVE_NUMBER are
undefined, they take their default value.
if CFG_FDC_HW_INIT is defined, then the function fdc_hw_init() is called
at the beginning of the fdc setup. The function
fdc_hw_init must be provided by the board source code. It is used to
make hardware dependant initializations.
CHANGELOG:
* Patch by Pierre Aubert , 05 Nov 2002
Hardware relative improvments in fdc booting
Best regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fdc.patch
Type: application/octet-stream
Size: 4453 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20021105/9ed24173/attachment.obj
next reply other threads:[~2002-11-05 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 16:57 Pierre AUBERT [this message]
2002-11-10 17:01 ` [U-Boot-Users] FDC patch Wolfgang Denk
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=3DC7F897.FA17CA3D@staubli.com \
--to=p.aubert@staubli.com \
--cc=u-boot@lists.denx.de \
/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