Messages in this thread | | | Subject | Re: VRAM protection in setup.c | Date | Sun, 20 Feb 2000 12:25:39 +0900 | From | Akira YOSHIYAMA <> |
| |
Hi,
From: Jeff Garzik <jgarzik@mandrakesoft.com> Subject: Re: VRAM protection in setup.c Date: Sat, 19 Feb 2000 14:25:26 -0500 Message-ID: <38AEEE26.40D29645@mandrakesoft.com>
> > static struct resource vram_resource = > > { "Video RAM area", 0xa0000, 0xbffff, IORESOURCE_MEM | IORESOURCE_AUTO }; > > > > and I met Tux penguin again. But, my box did hang up when loading > > pcmcia modules. Perhaps, my change might occur this problem. So, > > tell me more smart fix. > > Linus has explained his reasoning for leaving it at _BUSY. I disagree > but c'est la vie. > The solution is to remove all resource checks for that region from all > drivers, and hope and pray that everything plays nice together. :)
Yes, I guessed so.
> Since this region is really a special case, we might wind up with some > sort of resource access controller which arbitrates access to this > region. We need to do this so that PCI VGA cards may share regions...
So, I think we needed:
1)remap that region by vga16fb.c to access it. 2)add an argument to request_*resource() to specify enforced request (like -f for commands).
and, so on.
Thanks,
A.Yoshiyama(yosshy@debian.or.jp)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |