lkml.org 
[lkml]   [2003]   [Apr]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Flame Linus to a crisp!
John Bradford wrote:
> With open hardware designs, there would be no problem with
> documentation not being available to write drivers.

See below...

> Incidently, using the Transmeta CPUs, is it not possible for the user
> to replace the controlling software with their own code? I.E. not
> bother with X86 compatibility at all, but effectively design your own
> CPU? Couldn't we make the first Lin-PU this way?

In theory; in practice we have no access to documentation. See above...

That makes Transmeta part of the _old_ industry :)

I believe present Transmeta CPUs are quite specialised for x86
behaviour (memory model etc.) anyway. When you're running on a CPU
like that, there's probably little to be gained from changing to a
different front-end instruction set.
Special tricks like non-cache-ping-ponging locks and faster interrupt
handling might improve performance, but probably require a change of
the hardware to implement.

-- Jamie
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:34    [from the cache]
©2003-2011 Jasper Spaans