> Is vmalloc32 == vmalloc? (Found no vmalloc32 in the sources of
> 2.4.0test1[-ac13])
vmalloc_32. This uses GFP_KERNEL so memory on a big box comes from the low
960Mb
> Well, all I can say is the patch works as much as disableling
> CONFIG_HIGHMEM. In both ways the BUG is not hit, and the TV-card puts
> things to screen.
TV card to screen doesnt go via main memory and mmap or shouldnt
> bttv does not change the dma_mask, so it is 0xFFFFFFFF, and if i
> understand this right, the dma can access 4GB of RAM.
THat is right
> Also the DMA-transfer to screen goes to 0xE2000000 at my setup. The
> offending address was around 0x37AAXXXX. The page_address is needed for
> creation of some RISC-code (make_vbitab)
Ah.. that would make sense. Maybe I missed a vmalloc. The fix is wrong I think
but the bug would appear to be real
-
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/
This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:26 EST