On Sun, Apr 08, 2007 at 05:26:45PM +0400, Sergei Shtylyov wrote:
> If you read the comment to insert_resource() you'll see that it works
> contrarywise, i. e. the inserted resource is made parent of the conflicting
> ones. I.e. it should't work as you're intending it to.
why don't you think I haven't testet this ?
00000000-03bfffff : PCIT IO
00000000-0000001f : dma1
00000020-00000021 : pic1
00000040-0000005f : timer
00000060-0000006f : keyboard
00000080-0000008f : dma page reg
000000a0-000000a1 : pic2
000000c0-000000df : dma2
000002f8-000002ff : serial
000003c0-000003df : cirrusfb
000003f8-000003ff : serial
00000c80-00000c83 : EISA device @@@0000
00000cf8-00000cfb : PCI config addr
00000cfc-00000cff : PCI config data
00001000-000010ff : Madge Smart 16/4 EISA Ringnode
00001400-000014ff : Madge Smart 16/4 EISA Ringnode
00001800-000018ff : Madge Smart 16/4 EISA Ringnode
00001c00-00001cff : Madge Smart 16/4 EISA Ringnode
that's exactly what I wrote.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
|