[lkml]   [2006]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/2] Initial generic hypertransport interrupt support.
Andi Kleen <> writes:

> (Eric W. Biederman) writes:
>> This patch implements two functions ht_create_irq and ht_destroy_irq
>> for use by drivers. Several other functions are implemented as helpers
>> for arch specific irq_chip handlers.
> What do you want to use it for? Normally all HT configuration should be handled
> by the BIOS and not messed with by the kernel.

I don't believe this is a typical HT configuration as you are thinking of it.

There is a hypertransport capability that implements a rough equivalent
of a per device ioapic. It is quite similar to MSI but with a different
register level interface.

Since native hypertransport devices do not implement a pin emulation mode
as native pci express devices do so if you want an interrupt you must support
the native hypertransport method.

The pathscale ipath-ht400 driver already in the kernel tree uses these
and uses so an ugly hack to make work that broke in the last round of
the msi cleanups. I also know of a driver under development for a
device that uses these as well.

So I want to use this so I can get irqs from native hypertransport

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-07-12 05:09    [W:0.088 / U:0.216 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site