|To:||Kieran Fulke <email@example.com>|
|Subject:||Re: IRQ problem on cobalt / 2.6.6|
|From:||Peter Horton <firstname.lastname@example.org>|
|Date:||Mon, 17 May 2004 12:57:57 +0100|
|References:||<20040513183059.GA25743@getyour.pawsoff.org> <40A478B0.email@example.com> <20040516113622.GA14049@getyour.pawsoff.org> <20040516152113.GA9390@convergence.de> <20040516170445.GA4793@linux-mips.org> <40A87A81.firstname.lastname@example.org> <20040517114658.GA20884@getyour.pawsoff.org>|
|User-agent:||Mozilla Thunderbird 0.6 (Windows/20040502)|
Kieran Fulke wrote:
On Mon, May 17, 2004 at 09:40:33AM +0100, Peter Horton wrote:I've got no hardware here but the code looks roughly similiarAs the Cobalt's use Galileo timer 0 for clock interrupts we could use Galileo rather than count/compare for the HPT.Precision would be 50MHz rather than 125MHz but that shouldn't be a problem :-)is there any (uncomplicated) way of forcing the machine to assign a different IRQ to its single pci slot?
It's hard wired. P.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: IRQ problem on cobalt / 2.6.6, Kieran Fulke|
|Next by Date:||Re: IRQ problem on cobalt / 2.6.6, Kieran Fulke|
|Previous by Thread:||Re: IRQ problem on cobalt / 2.6.6, Kieran Fulke|
|Next by Thread:||Re: IRQ problem on cobalt / 2.6.6, Kieran Fulke|
|Indexes:||[Date] [Thread] [Top] [All Lists]|