From: Sergei Shtylyov <sshtylyov@ru.mvista.com> To: Olaf Hering <olaf@aepfle.de> Cc: Alan <alan@lxorguk.ukuu.org.uk>, linux-ide@vger.kernel.org, linuxppc-dev@ozlabs.org Subject: Re: pata_sl82c105 can not reserve IO region Date: Fri, 01 Dec 2006 22:05:28 +0300 [thread overview] Message-ID: <45707CF8.3090106@ru.mvista.com> (raw) In-Reply-To: <20061201183355.GA9701@aepfle.de> Olaf Hering wrote: >>The printk in pci_request_region has 'bar + 1', so 6 should be possible >>if i becomes 5. > Does the IO region of the last bar look correct? I'd say it looks suspicious since it's not adjacent to all the other regions... In fact, after looking at your /proc/ioports/ I can say that the BAR is actually unassigned and its *actual* value is 0 which the driver may not like (the ones that lspci show are the physical memory addresses not the actual I/O space addresses in this case). That's why the reservation fails. > 00:03.1 IDE interface: Symphony Labs SL82c105 (rev 05) (prog-if 8f [Master SecP SecO PriP PriO]) > Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- > Interrupt: pin A routed to IRQ 86 > Region 0: I/O ports at 3fd3000f000 [size=8] > Region 1: I/O ports at 3fd3000f010 [size=4] > Region 2: I/O ports at 3fd3000f020 [size=8] > Region 3: I/O ports at 3fd3000f030 [size=4] > Region 4: I/O ports at 3fd3000f040 [size=16] > Region 5: I/O ports at 3fd30000000 [size=16] > 00: ad 10 05 01 41 01 80 02 05 8f 01 01 08 48 80 00 > 10: 01 f0 00 00 11 f0 00 00 21 f0 00 00 31 f0 00 00 > 20: 41 f0 00 00 01 00 00 00 00 00 00 00 00 00 00 00 Well, BAR5 is indeed 0. > 30: 00 00 00 00 00 00 00 00 00 00 00 00 56 01 02 28 > 40: b3 08 ff 00 09 09 00 00 09 09 00 00 09 09 00 00 > 50: 09 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 70: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00 > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > name "ide" > linux,phandle 00d5cdc0 (14011840) > assigned-addresses 81001910 00000000 0000f000 00000000 00000008 81001914 > 00000000 0000f010 00000000 00000004 81001918 00000000 > 0000f020 00000000 00000008 8100191c 00000000 0000f030 > 00000000 00000004 81001920 00000000 0000f040 00000000 > 00000010 81001924 00000000 00000000 00000000 00000010 Yeah, the device tree has 0 for BAR5 too... WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sshtylyov@ru.mvista.com> To: Olaf Hering <olaf@aepfle.de> Cc: linux-ide@vger.kernel.org, Alan <alan@lxorguk.ukuu.org.uk>, linuxppc-dev@ozlabs.org Subject: Re: pata_sl82c105 can not reserve IO region Date: Fri, 01 Dec 2006 22:05:28 +0300 [thread overview] Message-ID: <45707CF8.3090106@ru.mvista.com> (raw) In-Reply-To: <20061201183355.GA9701@aepfle.de> Olaf Hering wrote: >>The printk in pci_request_region has 'bar + 1', so 6 should be possible >>if i becomes 5. > Does the IO region of the last bar look correct? I'd say it looks suspicious since it's not adjacent to all the other regions... In fact, after looking at your /proc/ioports/ I can say that the BAR is actually unassigned and its *actual* value is 0 which the driver may not like (the ones that lspci show are the physical memory addresses not the actual I/O space addresses in this case). That's why the reservation fails. > 00:03.1 IDE interface: Symphony Labs SL82c105 (rev 05) (prog-if 8f [Master SecP SecO PriP PriO]) > Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- > Interrupt: pin A routed to IRQ 86 > Region 0: I/O ports at 3fd3000f000 [size=8] > Region 1: I/O ports at 3fd3000f010 [size=4] > Region 2: I/O ports at 3fd3000f020 [size=8] > Region 3: I/O ports at 3fd3000f030 [size=4] > Region 4: I/O ports at 3fd3000f040 [size=16] > Region 5: I/O ports at 3fd30000000 [size=16] > 00: ad 10 05 01 41 01 80 02 05 8f 01 01 08 48 80 00 > 10: 01 f0 00 00 11 f0 00 00 21 f0 00 00 31 f0 00 00 > 20: 41 f0 00 00 01 00 00 00 00 00 00 00 00 00 00 00 Well, BAR5 is indeed 0. > 30: 00 00 00 00 00 00 00 00 00 00 00 00 56 01 02 28 > 40: b3 08 ff 00 09 09 00 00 09 09 00 00 09 09 00 00 > 50: 09 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 70: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00 > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > name "ide" > linux,phandle 00d5cdc0 (14011840) > assigned-addresses 81001910 00000000 0000f000 00000000 00000008 81001914 > 00000000 0000f010 00000000 00000004 81001918 00000000 > 0000f020 00000000 00000008 8100191c 00000000 0000f030 > 00000000 00000004 81001920 00000000 0000f040 00000000 > 00000010 81001924 00000000 00000000 00000000 00000010 Yeah, the device tree has 0 for BAR5 too... WBR, Sergei
next prev parent reply other threads:[~2006-12-01 19:04 UTC|newest] Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-30 16:52 pata_sl82c105 can not reserve IO region Olaf Hering 2006-11-30 17:10 ` Alan 2006-11-30 18:47 ` Olaf Hering 2006-12-01 18:34 ` Olaf Hering 2006-12-01 18:58 ` Alan 2006-12-01 19:05 ` Sergei Shtylyov [this message] 2006-12-01 19:05 ` Sergei Shtylyov 2006-12-01 21:53 ` Benjamin Herrenschmidt 2006-12-01 21:53 ` Benjamin Herrenschmidt 2006-12-01 22:15 ` Alan 2006-12-01 22:15 ` Alan 2006-12-01 22:19 ` Benjamin Herrenschmidt 2006-12-01 22:19 ` Benjamin Herrenschmidt 2006-12-02 14:36 ` U-Boot allocating PCI I/O space from 0 (Was: pata_sl82c105 can not reserve IO region) Sergei Shtylyov 2006-12-02 14:36 ` [U-Boot-Users] " Sergei Shtylyov 2006-12-02 16:33 ` Sergei Shtylyov 2006-12-02 16:33 ` [U-Boot-Users] " Sergei Shtylyov 2006-12-26 20:53 ` Sergei Shtylyov 2006-12-26 20:53 ` Sergei Shtylyov 2006-12-03 23:39 ` pata_sl82c105 can not reserve IO region Alan 2006-12-03 23:39 ` Alan 2006-12-03 17:12 ` Olaf Hering 2006-12-03 22:24 ` Olaf Hering 2006-12-03 23:23 ` Alan 2006-12-04 0:30 ` Olaf Hering 2006-12-04 9:21 ` Olaf Hering 2006-12-03 23:07 ` Alan 2006-12-04 12:38 ` [PATCH] mark PCI resource with start 0 as unassigned Olaf Hering 2006-12-04 12:44 ` Segher Boessenkool 2006-12-04 12:50 ` Sergei Shtylyov 2006-12-04 12:50 ` Sergei Shtylyov 2006-12-04 12:54 ` Segher Boessenkool 2006-12-04 12:54 ` Segher Boessenkool 2006-12-04 13:08 ` Sergei Shtylyov 2006-12-04 13:08 ` Sergei Shtylyov 2006-12-04 13:21 ` Alan 2006-12-04 13:25 ` Segher Boessenkool 2006-12-04 13:25 ` Segher Boessenkool 2006-12-04 14:15 ` Alan 2007-08-01 14:22 ` Sergei Shtylyov 2007-08-01 14:22 ` Sergei Shtylyov 2007-08-01 15:51 ` Alan Cox 2007-08-01 15:51 ` Alan Cox 2007-08-06 18:04 ` Segher Boessenkool 2007-08-06 18:04 ` Segher Boessenkool 2007-08-06 19:52 ` Alan Cox 2007-08-06 19:52 ` Alan Cox 2007-08-06 22:14 ` Benjamin Herrenschmidt 2007-08-06 22:14 ` Benjamin Herrenschmidt 2006-12-04 13:27 ` Sergei Shtylyov 2006-12-04 13:27 ` Sergei Shtylyov 2006-12-04 14:22 ` What is the correct way to indicate an unassigned PCI resource ? Alan 2006-12-04 14:34 ` Sergei Shtylyov 2006-12-04 14:34 ` Sergei Shtylyov 2006-12-04 14:44 ` Alan 2006-12-04 15:40 ` Sergei Shtylyov 2006-12-04 15:40 ` Sergei Shtylyov 2006-12-04 15:55 ` Sergei Shtylyov 2006-12-04 15:55 ` Sergei Shtylyov 2006-12-04 20:53 ` Guennadi Liakhovetski 2006-12-04 20:53 ` Guennadi Liakhovetski 2006-12-05 4:43 ` Benjamin Herrenschmidt 2006-12-05 4:43 ` Benjamin Herrenschmidt 2006-12-05 4:41 ` Benjamin Herrenschmidt 2006-12-05 4:41 ` Benjamin Herrenschmidt 2006-12-05 8:15 ` Olaf Hering 2006-12-05 8:15 ` Olaf Hering 2006-12-05 20:19 ` Benjamin Herrenschmidt 2006-12-05 20:19 ` Benjamin Herrenschmidt 2006-12-05 21:26 ` Sergei Shtylyov 2006-12-05 21:26 ` Sergei Shtylyov 2007-01-04 17:49 ` Olaf Hering 2007-01-04 21:30 ` Benjamin Herrenschmidt 2007-01-05 10:26 ` Olaf Hering 2007-01-05 10:26 ` Olaf Hering 2007-01-05 12:05 ` Benjamin Herrenschmidt 2007-01-05 12:05 ` Benjamin Herrenschmidt 2006-12-05 10:51 ` Gabriel Paubert 2006-12-05 10:51 ` Gabriel Paubert 2006-12-05 12:38 ` Sergei Shtylyov 2006-12-05 12:38 ` Sergei Shtylyov 2006-12-05 17:37 ` Grant Grundler 2006-12-05 17:37 ` Grant Grundler 2006-12-05 19:22 ` Sergei Shtylyov 2006-12-05 19:22 ` Sergei Shtylyov 2006-12-04 12:56 ` [PATCH] mark PCI resource with start 0 as unassigned Olaf Hering 2006-12-04 13:05 ` Segher Boessenkool 2006-12-04 12:47 ` Sergei Shtylyov 2006-12-04 12:40 ` [PATCH] add delay around sl82c105_reset_engine calls Olaf Hering 2006-12-04 13:02 ` Alan 2006-12-04 13:12 ` Olaf Hering 2007-01-04 6:42 ` Olaf Hering 2007-01-04 10:53 ` Alan
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=45707CF8.3090106@ru.mvista.com \ --to=sshtylyov@ru.mvista.com \ --cc=alan@lxorguk.ukuu.org.uk \ --cc=linux-ide@vger.kernel.org \ --cc=linuxppc-dev@ozlabs.org \ --cc=olaf@aepfle.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.