public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: root@chaos.analogic.com
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Problem with ioremap which returns NULL in 2.6 kernel
Date: Wed, 02 Jun 2004 17:26:36 +0200	[thread overview]
Message-ID: <40BDF1AC.7070209@shadowconnect.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0406021024400.3280@chaos>

Hello,

Richard B. Johnson wrote:
>>>>>>>My preferred approach would be:  consider that the hardware does not
>>>>>>>need the entire 0x8000000-byte area mapped.  Plain and simple.
>>>>>>>This is a "don't do that" situation, and that renders the other
>>>>>>>questions moot :)  You should only be mapping what you need to map.
>>>>>>Okay, i'll let try it out with only 64MB.
>>>>>Why do you need 64MB, even?  :)
>>>>I don't know how much space i need :-D But why does the device set the
>>>>size to 128MB then?
>>>Devices often export things you don't care about, such as direct access
>>>to internal chip RAM.
>>>Look through the driver that figure out the maximum value that the
>>>driver actually _uses_.  There is no need to guess.
>>Okay, i've looked at it, but i don't think i could simply use less
>>space, because (if i understand the I2O spec right :-D) the controller
>>returns me a address inside this window, where i could write the I2O
>>message. So i ask the controller, where do you want my request, then he
>>tells me a address...
>>If i only ioremap 64MB, and the controller tells me write at 80MB, i'm
>>in deep trouble :-D
> I2O, as seen from the PCI/Bus, is a bus! Right? You have a
> PCI/Bus controller that provides for an interface into
> I2O? Right? Can you do `cat /proc/pci` and show what device

Hope a lspci -v would also help :-D

If not i must ask for the output again...

First controller:

0000:00:09.0 I2O: Distributed Processing Technology SmartRAID V 
Controller (rev 02) (prog-if 01)
	Subsystem: Distributed Processing Technology 2400A UDMA Four Channel
	Flags: bus master, medium devsel, latency 64, IRQ 17
	BIST result: 00
	Memory at d0000000 (32-bit, prefetchable)
	Capabilities: [80] Power Management version 2

0000:00:09.1 PCI bridge: Distributed Processing Technology PCI Bridge 
(rev 02) (prog-if 00 [Normal decode])
	Flags: bus master, medium devsel, latency 64
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
	Expansion ROM at 0000a000 [disabled] [size=4K]
	Capabilities: [68] Power Management version 2


Second controller:

0000:00:0c.0 I2O: Distributed Processing Technology SmartRAID V 
Controller (rev 02) (prog-if 01)
	Subsystem: Distributed Processing Technology 2400A UDMA Four Channel
	Flags: bus master, medium devsel, latency 64, IRQ 19
	BIST result: 00
	Memory at d8000000 (32-bit, prefetchable)
	Capabilities: [80] Power Management version 2

0000:00:0c.1 PCI bridge: Distributed Processing Technology PCI Bridge 
(rev 02) (prog-if 00 [Normal decode])
	Flags: bus master, medium devsel, latency 64
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=64
	I/O behind bridge: 0000b000-0000bfff
	Expansion ROM at 0000b000 [disabled] [size=4K]
	Capabilities: [68] Power Management version 2

> you think it is?  I think you are attempting to access a bridge
> or something. I2O is supposed to be intelligent and to grab
> 64 megabytes of host address space is the anthesis of this.

I don't know the hardware part very vell :-( But because i'm not the 
author of the driver i don't think there is something wrong :-)


Best regards,



Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)

Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany

Phone:  +49 82 82/99 51-0
Fax:    +49 82 82/99 51-11

E-Mail: Markus.Lidel@shadowconnect.com
URL:    http://www.shadowconnect.com

  reply	other threads:[~2004-06-02 15:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 12:37 Problem with ioremap which returns NULL in 2.6 kernel Markus Lidel
2004-06-01 14:21 ` Jeff Garzik
2004-06-01 15:21   ` Markus Lidel
2004-06-01 17:08     ` Davide Rossetti
2004-06-02  8:59       ` Markus Lidel
2004-06-01 23:32     ` Jeff Garzik
2004-06-02  8:55       ` Markus Lidel
2004-06-02 13:23         ` Jeff Garzik
2004-06-02 13:49           ` Markus Lidel
2004-06-02 13:46             ` Jeff Garzik
2004-06-02 14:18               ` Markus Lidel
2004-06-02 14:39                 ` Richard B. Johnson
2004-06-02 15:26                   ` Markus Lidel [this message]
2004-06-02 15:45                     ` Richard B. Johnson
2004-06-03  2:41                       ` Stuart Young
2004-06-03  2:51                         ` Jeff Garzik
2004-06-03  8:38                           ` Markus Lidel
2004-06-03 11:42                         ` Richard B. Johnson
2004-07-16 11:19                         ` Richard B. Johnson
2004-06-02  0:09     ` Zwane Mwaikambo
2004-06-02 12:17       ` Markus Lidel
2004-06-04 20:16         ` Zwane Mwaikambo
2004-07-16 17:29         ` Zwane Mwaikambo
2004-07-16 17:30           ` Jeff Garzik
2004-07-17  0:30             ` Markus Lidel
2004-07-17  0:33           ` Markus Lidel

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=40BDF1AC.7070209@shadowconnect.com \
    --to=markus.lidel@shadowconnect.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    /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