On 9/8/05, Jim Ramsay <[EMAIL PROTECTED]> wrote:
> On 9/8/05, Matthew Dharm <[EMAIL PROTECTED]> wrote:
> > On Thu, Sep 08, 2005 at 11:14:36AM -0600, Jim Ramsay wrote:
> > > I think I have found a possible bug:
> > > [...]
> > > I suppose the scsi c
On 9/8/05, Matthew Dharm <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 08, 2005 at 11:14:36AM -0600, Jim Ramsay wrote:
> > I think I have found a possible bug:
> > [...]
> > I suppose the scsi code could be changed to guarantee that
> > srb->request_buffer is pag
he scsi code could be changed to guarantee that
srb->request_buffer is page-aligned or cache-aligned, but that seems
like the wrong solution for this bug.
Questions? Comments? Is this the right way to fix it?
--
Jim Ramsay
"Me fail English? That's unpossible!"
-
To unsubscr
e seen the occasion where a single IRQ is used to signal
both a DMA completion AND a hotplug event. Of course in this case the
hotplug event itself would be ignored completely.
So I would recommend getting rid of that check entirely.
--
Jim Ramsay
"Me fail English? That's unpossible!&qu
On 8/24/05, Jim Ramsay <[EMAIL PROTECTED]> wrote:
> On 8/24/05, Lukasz Kosewski <[EMAIL PROTECTED]> wrote:
> > On 8/24/05, Stefan Richter <[EMAIL PROTECTED]> wrote:
> > > >> Timers appear to operate in an atomic context, so timers should not be
> >
r
That's easy. I'll add it in my 'patch 4/3'
> - bunch of code cleanups
Haven't touched this, looks pretty clean to me
> - proper error handling
This may be something I'll have to stick my fingers in as I do more testing
> - actually making the patches wor
On 8/23/05, Jim Ramsay <[EMAIL PROTECTED]> wrote:
> Then I must have found an undocumented feature! I've applied this set
> of patches to a 2.6.11 kernel (with few problems) and ran into a bunch
> of "scheduling while atomic" errors when hotplugging a drive, culprit
ueue for hotplug requests to get
them out of the atomic interrupt handler context where they originate?
--
Jim Ramsay
"Me fail English? That's unpossible!"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
the issue that the new 2.6 xlinit code assumes that
you have a bios that will do *something* to your chip before handing
control over to the kernel, which is not always the case.
If you have a fix that is more correct, I'd be happy to test it for you!
--
Jim Ramsay
"Me fail English?
, the chip has not been initialized,
otherwise I initialize it.
--
Jim Ramsay
"Me fail English? That's unpossible!"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vge
hat in the 2.6 kernel.
So I copied the relevant 2.4 bits for non-i386 archs, and replaced the
call to 'var_to_pll' with the "new" stuff.
This seems to work for me. Enjoy!
--
Jim Ramsay
"Me fail English? That's unpossible!"
/*
* ATI Rage XL Initialization
eady execute the ati option rom via x86 emulator...
Maybe his mips FW does this, but mine doesn't. Any tips on how I can
do this in software?
--
Jim Ramsay
"Me fail English? That's unpossible!"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
er 255, ReferenceDivider
255, PostDivider 3(0)
< Other times it will hang here >
And that's all I get.
I'm assuming that most of my issues are due to the "Unsupported xclk
source" message. Any ideas what I can do about this, or where I can
go to learn more about how to
13 matches
Mail list logo
