From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Yu, Luming" Date: Tue, 16 Dec 2003 09:37:35 +0000 Subject: RE: Latest 2.4 IA64 Baseline (Bjorn) + Latest ACPI testing report Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-ia64@vger.kernel.org >> > >> 3.alloc 0x0-0xcf7 from PCI IO for PCI Bus 00:00 failed (Known issue) >> > >> > Since VGA console driver faile to allocate that port range, why it still can work? >> > Does it mean 0x3c0-0x3df is inessential to VGA console driver. >> >> No, I think those ports are essential. The driver just uses them, >> even if the allocation fails. I have a 2.6 patch that cleans this >> up. It doesn't change any functionality; it just gets rid of the >> message and makes /proc/ioports more correct. I'll submit it as >> soon as it makes sense to put non-critical changes into 2.6. >I didn't answer this quite right. The VGA driver allocates ports >0x3c0-0x3df early, and that allocation succeeds. Later, we >discover the PCI root bridges, and try to allocate the port ranges >for each. It's the PCI root bridge allocation that fails, because >it's trying to allocate a range that includes the VGA ports. >So we end up with something like this in /proc/ioports (this is a >made-up example, but same idea): > > 000003c0-000003df : vga+ > 00004000-00009fff : PCI Bus 00:00 > 00004000-000040ff : sym53c8xx > 00004100-000041ff : sym53c8xx > >when we should have this: > > 00000000-00000cf7 : PCI Bus 00:00 > 000003c0-000003df : vga+ > 00004000-00009fff : PCI Bus 00:00 > 00004000-000040ff : sym53c8xx > 00004100-000041ff : sym53c8xx > >The patch just changes the PCI root bridge allocation so that >instead of failing if part of the range has already been allocated, >it inserts a new range up one level, so it encloses the previous >VGA allocation. Could you let me see what are you patch doing. I think "To bus device, resources returned from _CRS method means that bus device will supply those resouces to its children devices. So it's unreasonable to call request_resource for them." I have a patch for above statement. Please take http://bugzilla.kernel.org/show_bug.cgi?id85 a look. Thanks, Luming