Greetings,
I think we�ve hit a bug with HIMEM and vmalloc(); after I turned on HIGHMEM
I get similar results: every second frame or so is either bright pink, dark
green, but nothing normal. Memory allocation looks normal from debugging.
- Nemosoft
On 12-Sep-01 Oliver Neukum wrote:
>> The second bug report said the module works fine when the person limits
>> his
>> memory to 960 MB (how, I dont know). With full memory, he gets artefacts
>
> With a 'mem=' kernel command line I presume.
>
>> which to me suggests the second frame buffer is allocated, but somehow in
>> memory which isnt accessible (every other frame is bright pink --> filled
>> with 0xFF before YUV->RGB translation?)
>
> Not accessible by whom ?
> The USB controller or the CPU ? 1GB should be accessible to the USB
> controller.
>
>> Unfortunately Im not rich enough to put 1GB of RAM in my machine to test
>> this... ;-(
>
> If it is indeed a problem of accessability by the CPU you might use the
> patch
> Andrea Arcangeli has written which allows you the use highmen with 128MB.
>
> Regards
> Oliver
>
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
-----------------------------------------------------------------------------
Try SorceryNet! One of the best IRC-networks around! irc.sorcery.net:9000
URL: never IRC: nemosoft IscaBBS (bbs.isca.uiowa.edu): Nemosoft
>> Never mind the daylight <<
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
