From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
akpm@osdl.org, linux-ide@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] ide: Stop mapping ROMs
Date: Sat, 23 Jun 2007 22:54:24 +0400 [thread overview]
Message-ID: <467D6C60.5050305@ru.mvista.com> (raw)
In-Reply-To: <200706231942.31049.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
>>>Various old IDE drivers go mapping ROM devices for no apparent reason and
>>>without using the ROM mapping API we now have. They don't actually use
>> Hm, do you mean the sysfs based aproach? I've tried that and somehow it
>>failed to work for me -- that's because I deferred removing this stuff from
>>the drivers.
> Could you elaborate a bit about sysfs based approach?
You can see the code is in drivers/pci/pci-sysfs.c.
I have HPT370 as PCI device 11 -- and it fails with it in this way:
root@192.168.222.8:~# ls -l /sys/devices/pci0000\:00/0000\:00\:0b.0/rom
-r------- 1 root root 131072 Jun 23 21:36 21:36
/sys/devices/pci0000:00/0000:00:0b.0/rom
root@192.168.222.8:~# echo 1 > /sys/devices/pci0000\:00/0000\:00\:0b.0/rom
root@192.168.222.8:~# od -h /sys/devices/pci0000\:00/0000\:00\:0b.0/rom
0000000
> If it indeed doesn't work we should ping PCI people about it.
As you can see, the file isn't empty but 'od' fails to dump anything --
I've just verified this still happens with the most recent i386 kernel.
I suspect this is because ROM mapping fails... :-/
>>>mapped so rather than port them lets just junk it for the next -rc1.
>> I'd agree to the patch -- the drivers were mapping ROMs in a bad way,
>>often using the default addresses.
> I added your ACK to the patch.
Well, if you think it's important... :-)
(Yeah, I've read the recent LKML thread. :-)
> Thanks,
> Bart
MBR, Sergei
next prev parent reply other threads:[~2007-06-23 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 13:22 [PATCH] ide: Stop mapping ROMs Alan Cox
2007-06-22 13:59 ` Sergei Shtylyov
2007-06-23 17:42 ` Bartlomiej Zolnierkiewicz
2007-06-23 18:54 ` Sergei Shtylyov [this message]
2007-06-23 17:42 ` Bartlomiej Zolnierkiewicz
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=467D6C60.5050305@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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;
as well as URLs for NNTP newsgroup(s).