On Wed, 21 Jun 2006, Benjamin Herrenschmidt wrote: > No, our hardware interrupt numbers are an encoded form containing the > geographical location of the device :) so they are 24 bits at least (and > we have a platform coming where they can be 64 bits). PICs with build in GPSses? And I thought we had weird hardware.... - 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://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [patch 0/3] 2.6.17 radix-tree: updates and lockless
- From: Benjamin Herrenschmidt <[email protected]>
- Re: [patch 0/3] 2.6.17 radix-tree: updates and lockless
- References:
- [patch 0/3] 2.6.17 radix-tree: updates and lockless
- From: Nick Piggin <[email protected]>
- Re: [patch 0/3] 2.6.17 radix-tree: updates and lockless
- From: Andrew Morton <[email protected]>
- Re: [patch 0/3] 2.6.17 radix-tree: updates and lockless
- From: Benjamin Herrenschmidt <[email protected]>
- Re: [patch 0/3] 2.6.17 radix-tree: updates and lockless
- From: Andrew Morton <[email protected]>
- Re: [patch 0/3] 2.6.17 radix-tree: updates and lockless
- From: Benjamin Herrenschmidt <[email protected]>
- Re: [patch 0/3] 2.6.17 radix-tree: updates and lockless
- From: Christoph Lameter <[email protected]>
- Re: [patch 0/3] 2.6.17 radix-tree: updates and lockless
- From: Benjamin Herrenschmidt <[email protected]>
- [patch 0/3] 2.6.17 radix-tree: updates and lockless
- Prev by Date: Re: cfq-iosched.c:RB_CLEAR_COLOR
- Next by Date: Re: [PATCH 0/25] Decouple IRQ issues (MSI, i386, x86_64, ia64)
- Previous by thread: Re: [patch 0/3] 2.6.17 radix-tree: updates and lockless
- Next by thread: Re: [patch 0/3] 2.6.17 radix-tree: updates and lockless
- Index(es):
 |