Re: [PATCH 03/13] [RFC] ipath copy routines

[Robert Walsh <rjwalsh@pathscale.com>]

> > Any chance we could get these moved into the x86_64 arch directory,
> > then?
> 
> That would make sense.  Give it a non-ipath-related name and require that
> all architectures which wish to run this driver must implement that
> (documented) function.
> 
> And, in Kconfig, make sure that architectures which don't implement that
> library function do not attempt to build this driver.  To avoid breaking
> `make allmodconfig'.

Sounds good.  I'll get something together next week.

> >  We have to do double-word copies, or our chip gets unhappy.
> 
> In what form is this chip available?  As a standard PCI/PCIX card which
> people will want to plug into power4/ia64/x86 machines?  Or is it in some
> way exclusively tied to x86_64?

It's a HyperTransport card, not PCI/PCIe/PCIX.  It plugs into the HTX
slot on a suitably-equipped motherboard.  On some machines, it's
available on the motherboard itself (e.g. the Linux Networx LS/X.)

Regards,
 Robert.

-- 
Robert Walsh                                 Email: rjwalsh@pathscale.com
PathScale, Inc.                              Phone: +1 650 934 8117
2071 Stierlin Court, Suite 200                 Fax: +1 650 428 1969
Mountain View, CA 94043.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/