On 24.12.2009, at 01:08, Aurelien Jarno wrote:
> On Thu, Dec 24, 2009 at 12:39:36AM +0100, Laurent Vivier wrote:
>> Le mercredi 23 décembre 2009 à 10:55 +, Paul Brook a écrit :
The problem is that the whole define is just plain wrong which tells me
that the code is using the bswap f
On Thu, Dec 24, 2009 at 12:39:36AM +0100, Laurent Vivier wrote:
> Le mercredi 23 décembre 2009 à 10:55 +, Paul Brook a écrit :
> > > The problem is that the whole define is just plain wrong which tells me
> > > that the code is using the bswap functions incorrectly. This really
> > > needs to b
Le mercredi 23 décembre 2009 à 10:55 +, Paul Brook a écrit :
> [2] My guess is that the code is cribbed from elsewhere, and the original
> source gave the CPU direct access to the ch->regs[] array.
In fact it comes from Mac-On-Linux, src/drivers/dbdma.c
Laurent
--
- laur
Le mercredi 23 décembre 2009 à 10:55 +, Paul Brook a écrit :
> > The problem is that the whole define is just plain wrong which tells me
> > that the code is using the bswap functions incorrectly. This really
> > needs to be fixed by someone who knows the dbdma device. I don't see how
> > calli
> The problem is that the whole define is just plain wrong which tells me
> that the code is using the bswap functions incorrectly. This really
> needs to be fixed by someone who knows the dbdma device. I don't see how
> calling incorrect calls even more incorrect makes any difference.
The real pr
On 23.12.2009, at 11:06, Aurelien Jarno wrote:
> On Wed, Dec 23, 2009 at 10:29:53AM +0100, Alexander Graf wrote:
>>
>> On 23.12.2009, at 07:12, Aurelien Jarno wrote:
>>
>>> On Tue, Dec 22, 2009 at 02:45:17PM +0100, Alexander Graf wrote:
When we get an MMIO request, we always get variables
On Wed, Dec 23, 2009 at 10:29:53AM +0100, Alexander Graf wrote:
>
> On 23.12.2009, at 07:12, Aurelien Jarno wrote:
>
> > On Tue, Dec 22, 2009 at 02:45:17PM +0100, Alexander Graf wrote:
> >> When we get an MMIO request, we always get variables in host endianness.
> >> The
> >> only time we need t
On 23.12.2009, at 07:12, Aurelien Jarno wrote:
> On Tue, Dec 22, 2009 at 02:45:17PM +0100, Alexander Graf wrote:
>> When we get an MMIO request, we always get variables in host endianness. The
>> only time we need to actually reverse byte order is when we read bytes from
>> guest memory.
>>
>> A
On Tue, Dec 22, 2009 at 02:45:17PM +0100, Alexander Graf wrote:
> When we get an MMIO request, we always get variables in host endianness. The
> only time we need to actually reverse byte order is when we read bytes from
> guest memory.
>
> Apparently the DBDMA implementation is different there. A
On Tue, Dec 22, 2009 at 01:07:20PM +0100, Alexander Graf wrote:
> Michael S. Tsirkin wrote:
> > On Tue, Dec 22, 2009 at 11:24:18AM +0100, Alexander Graf wrote:
> >
> >> When we get an MMIO request, we always get variables in host endianness.
> >> The
> >> only time we need to actually reverse b
Michael S. Tsirkin wrote:
> On Tue, Dec 22, 2009 at 11:24:18AM +0100, Alexander Graf wrote:
>
>> When we get an MMIO request, we always get variables in host endianness. The
>> only time we need to actually reverse byte order is when we read bytes from
>> guest memory.
>>
>> Apparently the DBDMA
On Tue, Dec 22, 2009 at 11:24:18AM +0100, Alexander Graf wrote:
> When we get an MMIO request, we always get variables in host endianness. The
> only time we need to actually reverse byte order is when we read bytes from
> guest memory.
>
> Apparently the DBDMA implementation is different there. A
12 matches
Mail list logo
