From: Jens Schmalzing <jens.schmalzing@physik.uni-muenchen.de>
To: Matthew Wilcox <willy@debian.org>
Cc: debian-kernel@lists.debian.org, linux-scsi@vger.kernel.org
Subject: Re: CONFIG_SCSI_SYM53C8XX_IOMAPPED
Date: 16 Sep 2004 20:34:38 +0200 [thread overview]
Message-ID: <hhllfat64h.fsf@theorie.physik.uni-muenchen.de> (raw)
In-Reply-To: 20040916153142.GM642@parcelfarce.linux.theplanet.co.uk
Hi,
Matthew Wilcox writes:
> > It outputs a "can't map PCI MMIO region" and does nothing at all.
> Interesting. This can only happen if ioremap() returns NULL.
Sorry. I got the message completely wrong. I really was:
| PCI: Enabling device 0000:00:0c.0 (0000 -> 0003)
| sym.0.12.0: MMIO base address disabled.
> lspci -v of that device would be interesting to see.
| 0000:00:0c.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 02)
| Flags: bus master, medium devsel, latency 128, IRQ 13
| I/O ports at 1000 [size=256]
| [virtual] Memory at c0000000 (32-bit, non-prefetchable) [size=256]
> > CONFIG_SCSI_SYM53C8XX_2=m
> > CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
> > CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
> > CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
> > # CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
> Those are good config options.
So I used them for a test kernel, built from kernel-source-2.6.8 and
your little debugging patch applied. What happened is this:
| map 0xc4000000 length 128 returned 0xf4000000
and the kernel initialized the SCSI controller correctly - as I could
verify, this is due to the backported patch from 2.6.9-rc2 that Hollis
Blanchard sent here earlier in Bug#271852. So that problem will be
solved in the next revision.
Thanks for your time and help.
Regards, Jens.
--
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-09-16 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <hhsm9iv8ws.fsf@alsvidh.mathematik.uni-muenchen.de>
2004-09-16 14:13 ` CONFIG_SCSI_SYM53C8XX_IOMAPPED Matthew Wilcox
2004-09-16 14:22 ` CONFIG_SCSI_SYM53C8XX_IOMAPPED Jens Schmalzing
2004-09-16 15:31 ` CONFIG_SCSI_SYM53C8XX_IOMAPPED Matthew Wilcox
2004-09-16 18:34 ` Jens Schmalzing [this message]
2004-09-16 20:14 ` CONFIG_SCSI_SYM53C8XX_IOMAPPED Matthew Wilcox
2004-09-16 20:21 ` CONFIG_SCSI_SYM53C8XX_IOMAPPED Jens Schmalzing
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=hhllfat64h.fsf@theorie.physik.uni-muenchen.de \
--to=jens.schmalzing@physik.uni-muenchen.de \
--cc=debian-kernel@lists.debian.org \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@debian.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