On Sun, Feb 22, 2009 at 01:51:38PM -0800, W. van den Akker wrote:
> On Monday 16 February 2009 11:18:28 W. van den Akker wrote:
> > > On Wed, Feb 11, 2009 at 12:07 AM, Luis R. Rodriguez
> > >
> > > wrote:
> > >> So I've gone back to the drawing board, and reviewed this issue
> > >> as thoroughly a
On Mon, Feb 23, 2009 at 10:19 PM, W. van den Akker wrote:
>> On Mon, Feb 23, 2009 at 1:08 PM, W. van den Akker
>> wrote:
>>> On Monday 23 February 2009 18:48:09 Luis R. Rodriguez wrote:
On Mon, Feb 23, 2009 at 9:45 AM, W. van den Akker
>>> wrote:
> On Monday 23 February 2009 18:31:46 L
> On Mon, Feb 23, 2009 at 1:08 PM, W. van den Akker
> wrote:
>> On Monday 23 February 2009 18:48:09 Luis R. Rodriguez wrote:
>>> On Mon, Feb 23, 2009 at 9:45 AM, W. van den Akker
>> wrote:
>>> > On Monday 23 February 2009 18:31:46 Luis R. Rodriguez wrote:
>>> >> On Sun, Feb 22, 2009 at 01:51:38PM
On Mon, Feb 23, 2009 at 1:08 PM, W. van den Akker wrote:
> On Monday 23 February 2009 18:48:09 Luis R. Rodriguez wrote:
>> On Mon, Feb 23, 2009 at 9:45 AM, W. van den Akker
> wrote:
>> > On Monday 23 February 2009 18:31:46 Luis R. Rodriguez wrote:
>> >> On Sun, Feb 22, 2009 at 01:51:38PM -0800, W
On Monday 23 February 2009 18:48:09 Luis R. Rodriguez wrote:
> On Mon, Feb 23, 2009 at 9:45 AM, W. van den Akker
wrote:
> > On Monday 23 February 2009 18:31:46 Luis R. Rodriguez wrote:
> >> On Sun, Feb 22, 2009 at 01:51:38PM -0800, W. van den Akker wrote:
> >> > On Monday 16 February 2009 11:18:2
On Monday 23 February 2009 18:48:09 Luis R. Rodriguez wrote:
> On Mon, Feb 23, 2009 at 9:45 AM, W. van den Akker
wrote:
> > On Monday 23 February 2009 18:31:46 Luis R. Rodriguez wrote:
> >> On Sun, Feb 22, 2009 at 01:51:38PM -0800, W. van den Akker wrote:
> >> > On Monday 16 February 2009 11:18:2
On Mon, Feb 23, 2009 at 9:45 AM, W. van den Akker wrote:
> On Monday 23 February 2009 18:31:46 Luis R. Rodriguez wrote:
>> On Sun, Feb 22, 2009 at 01:51:38PM -0800, W. van den Akker wrote:
>> > On Monday 16 February 2009 11:18:28 W. van den Akker wrote:
>> > > > On Wed, Feb 11, 2009 at 12:07 AM, L
On Monday 23 February 2009 18:31:46 Luis R. Rodriguez wrote:
> On Sun, Feb 22, 2009 at 01:51:38PM -0800, W. van den Akker wrote:
> > On Monday 16 February 2009 11:18:28 W. van den Akker wrote:
> > > > On Wed, Feb 11, 2009 at 12:07 AM, Luis R. Rodriguez
> > > >
> > > > wrote:
> > > >> So I've gone
On Monday 16 February 2009 11:18:28 W. van den Akker wrote:
> > On Wed, Feb 11, 2009 at 12:07 AM, Luis R. Rodriguez
> >
> > wrote:
> >> So I've gone back to the drawing board, and reviewed this issue
> >> as thoroughly as I can. The issue is PCI reads/writes can overlap
> >> with each other (not j
> On Wed, Feb 11, 2009 at 12:07 AM, Luis R. Rodriguez
> wrote:
>> So I've gone back to the drawing board, and reviewed this issue
>> as thoroughly as I can. The issue is PCI reads/writes can overlap
>> with each other (not just writes). This shouldn't generally be an
>> issue but if some reads tak
On Wed, Feb 11, 2009 at 12:07 AM, Luis R. Rodriguez
wrote:
> So I've gone back to the drawing board, and reviewed this issue
> as thoroughly as I can. The issue is PCI reads/writes can overlap
> with each other (not just writes). This shouldn't generally be an
> issue but if some reads take a whil
So I've gone back to the drawing board, and reviewed this issue
as thoroughly as I can. The issue is PCI reads/writes can overlap
with each other (not just writes). This shouldn't generally be an
issue but if some reads take a while, for example, there could be
another read/write on its way on anot
12 matches
Mail list logo