On Tue, 22 Nov 2011, Markus Armbruster wrote:
> Stefano Stabellini writes:
>
> > On Tue, 22 Nov 2011, Markus Armbruster wrote:
> >> Case 24 falls through to case 32, which overwrites all of case 24's
> >> work. Looks wrong. Git blames commit 0da2ea1b "fix endianness problem
> >> sharing the vid
Stefano Stabellini writes:
> On Tue, 22 Nov 2011, Markus Armbruster wrote:
>> Case 24 falls through to case 32, which overwrites all of case 24's
>> work. Looks wrong. Git blames commit 0da2ea1b "fix endianness problem
>> sharing the videoram buffer".
>>
>> Patching in a break is easy enough,
On Tue, 22 Nov 2011, Stefan Hajnoczi wrote:
> On Tue, Nov 22, 2011 at 10:06 AM, Markus Armbruster wrote:
> > Case 24 falls through to case 32, which overwrites all of case 24's
> > work. ÃÂ Looks wrong. ÃÂ Git blames commit 0da2ea1b "fix endianness
> > problem
> > sharing the videoram buffer".
On Tue, 22 Nov 2011, Markus Armbruster wrote:
> Case 24 falls through to case 32, which overwrites all of case 24's
> work. Looks wrong. Git blames commit 0da2ea1b "fix endianness problem
> sharing the videoram buffer".
>
> Patching in a break is easy enough, but since I don't actually
> underst
On Tue, Nov 22, 2011 at 10:06 AM, Markus Armbruster wrote:
> Case 24 falls through to case 32, which overwrites all of case 24's
> work. Looks wrong. Git blames commit 0da2ea1b "fix endianness problem
> sharing the videoram buffer".
>
> Patching in a break is easy enough, but since I don't actua
Case 24 falls through to case 32, which overwrites all of case 24's
work. Looks wrong. Git blames commit 0da2ea1b "fix endianness problem
sharing the videoram buffer".
Patching in a break is easy enough, but since I don't actually
understand how the function is used, I have no idea what exactly