On Fri, Feb 16, 2007 at 02:47:45PM -0800, Daniel Walker wrote:
> > > Gets pretty ugly .. The clocksource interface already has a positive
> > > rating to describe the "best" clocks in the system, which is used to
> > > return the "best" clock .. Where the maintainers of the system give each
> > >
On Fri, Feb 16, 2007 at 01:06:19PM -0800, Daniel Walker wrote:
> On Fri, 2007-02-16 at 14:34 -0500, Jeff Muizelaar wrote:
> > It think it would be better if you had sometime like
> > 'clocksource_get_clock_with_features()' that took flags describing the
> > needed ch
On Fri, Feb 16, 2007 at 10:44:15AM -0800, Randy Dunlap wrote:
> On Fri, 16 Feb 2007 13:30:14 -0500 Jeff Muizelaar wrote:
>
> > On Fri, Feb 16, 2007 at 11:30:56AM -0500, Frank Ch. Eigler wrote:
> > > Jeff Muizelaar <[EMAIL PROTECTED]> writes:
> > >
>
On Fri, Feb 16, 2007 at 09:02:44PM +0100, Andi Kleen wrote:
> Jeff Muizelaar <[EMAIL PROTECTED]> writes:
> >
> > The question is, what api should I be using? I need something that can
> > be called from inside interrupt handlers, and obviously the more
> > ac
On Fri, Feb 16, 2007 at 10:28:50AM -0800, Daniel Walker wrote:
> On Fri, 2007-02-16 at 13:10 -0500, Jeff Muizelaar wrote:
> > On Fri, Feb 16, 2007 at 09:45:21AM -0800, Daniel Walker wrote:
> > > I've been working on a patch set (below), to expose the clocksources
> >
On Fri, Feb 16, 2007 at 11:30:56AM -0500, Frank Ch. Eigler wrote:
> Jeff Muizelaar <[EMAIL PROTECTED]> writes:
>
> > I've built a tool with the goal of logging mmio writes and reads by
> > device drivers. See http://nouveau.freedesktop.org/wiki/MmioTrace.
>
> FWIW,
On Fri, Feb 16, 2007 at 09:45:21AM -0800, Daniel Walker wrote:
> I've been working on a patch set (below), to expose the clocksources
> used by generic time to multiple users . It would allow timestamps from
> different clocks in a generic way. It's not merged, but I'd appreciate
> any input
On Fri, Feb 16, 2007 at 09:45:21AM -0800, Daniel Walker wrote:
I've been working on a patch set (below), to expose the clocksources
used by generic time to multiple users . It would allow timestamps from
different clocks in a generic way. It's not merged, but I'd appreciate
any input either of
On Fri, Feb 16, 2007 at 11:30:56AM -0500, Frank Ch. Eigler wrote:
Jeff Muizelaar [EMAIL PROTECTED] writes:
I've built a tool with the goal of logging mmio writes and reads by
device drivers. See http://nouveau.freedesktop.org/wiki/MmioTrace.
FWIW, this is exactly a type of add-on trace
On Fri, Feb 16, 2007 at 10:28:50AM -0800, Daniel Walker wrote:
On Fri, 2007-02-16 at 13:10 -0500, Jeff Muizelaar wrote:
On Fri, Feb 16, 2007 at 09:45:21AM -0800, Daniel Walker wrote:
I've been working on a patch set (below), to expose the clocksources
used by generic time to multiple
On Fri, Feb 16, 2007 at 09:02:44PM +0100, Andi Kleen wrote:
Jeff Muizelaar [EMAIL PROTECTED] writes:
The question is, what api should I be using? I need something that can
be called from inside interrupt handlers, and obviously the more
accurate and the lower the overhead the better
On Fri, Feb 16, 2007 at 10:44:15AM -0800, Randy Dunlap wrote:
On Fri, 16 Feb 2007 13:30:14 -0500 Jeff Muizelaar wrote:
On Fri, Feb 16, 2007 at 11:30:56AM -0500, Frank Ch. Eigler wrote:
Jeff Muizelaar [EMAIL PROTECTED] writes:
I've built a tool with the goal of logging mmio writes
On Fri, Feb 16, 2007 at 01:06:19PM -0800, Daniel Walker wrote:
On Fri, 2007-02-16 at 14:34 -0500, Jeff Muizelaar wrote:
It think it would be better if you had sometime like
'clocksource_get_clock_with_features()' that took flags describing the
needed characteristics instead of the unwanted
On Fri, Feb 16, 2007 at 02:47:45PM -0800, Daniel Walker wrote:
Gets pretty ugly .. The clocksource interface already has a positive
rating to describe the best clocks in the system, which is used to
return the best clock .. Where the maintainers of the system give each
clock a rating.
I've built a tool with the goal of logging mmio writes and reads by
device drivers. See http://nouveau.freedesktop.org/wiki/MmioTrace.
I'd like to add support for recording a time stamp on each read and
write. Unfortunately, I am not sure which clock api I should use.
I had a look at blktrace
I've built a tool with the goal of logging mmio writes and reads by
device drivers. See http://nouveau.freedesktop.org/wiki/MmioTrace.
I'd like to add support for recording a time stamp on each read and
write. Unfortunately, I am not sure which clock api I should use.
I had a look at blktrace
I have built a tool with the goal of logging mmio writes and reads by
device drivers. I am sure anyone who has reverse engineered device
drivers can immediately see the use of such a tool. In particular I have
been trying to help with the nouveau project. The code for the tool is
based on the work
I have built a tool with the goal of logging mmio writes and reads by
device drivers. I am sure anyone who has reverse engineered device
drivers can immediately see the use of such a tool. In particular I have
been trying to help with the nouveau project. The code for the tool is
based on the work
I am having dificulty getting an ASIX AX88140 ethernet card to work under
the 2.4.3 kernel.
It works perfectly under a 2.2.19 kernel and is found properly, but when
trying the 2.4.3 kernel it fails with the message:
tulip: eth1: MMIO region (0x0@0x0) unavailable, aborting
tulip-diag
I am having dificulty getting an ASIX AX88140 ethernet card to work under
the 2.4.3 kernel.
It works perfectly under a 2.2.19 kernel and is found properly, but when
trying the 2.4.3 kernel it fails with the message:
tulip: eth1: MMIO region (0x0@0x0) unavailable, aborting
tulip-diag
20 matches
Mail list logo
