From: Andre Bonin <kernel@bonin.ca>
To: Tomasz Rola <rtomek@cis.com.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI coprocessors
Date: Wed, 15 Sep 2004 11:15:07 -0400 [thread overview]
Message-ID: <41485C7B.40202@bonin.ca> (raw)
In-Reply-To: <Pine.LNX.3.96.1040915164509.26011A-100000@pioneer.space.nemesis.pl>
Thank you for all your input on this. Of course i could do many things
on the board. The idea of the library is that a programmer would create
the fpga image file by him/herself and then put it in the library. The
kernel driver and the library does the decision if its worth putting on
the chip or not (that's optional, you could force it on chip).
Tomasz Rola wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>
>>Which leads me to my questions:
>>
>>1) Is their support for having two different 'machine types' within one
>>kernel? that is for example, certain executables for intel would get run
>>on an intel processor, and others would get run on processor with type XXXX.
>>
>>
>
>There are probably no impossible things - some may be unthinkable but once
>they are thought of, they can be done too. But this one thing may be
>rather difficult (just my opinion).
>
>
Yes i think so too, especially since it will be my first kernel module
(and anxiously waiting the next release of the o'reilly book for
refference).
>How about porting kernel and gcc to your fp-cpu and use pci as a
>kind of fast network-like interconnect? After loading a kernel into it
>somehow, boot it with nfs root and run the rest from nfs server that would
>be provided by a host Intel machine.
>
>
System-on-chips have been done before, and could be integrated into the
kernel like you said. But RAM becomes a problem. Since its only a
student project, we have a limit on the adressing width for the ram
(32bit addressing becomes 32 wires, that's a lot of wirewraping :) ).
>That would require less changes to a kernel, probably. A module for a
>host, for example - some "pci-net". And port of a kernel to your fp-cpu
>which should be easier than putting support for heterogenous
>multiprocessors...
>
>
I agree but i think that goes beyond the scope of the project. Though i
will consider it. Thanks for your input!
>- --
>** A C programmer asked whether computer had Buddha's nature. **
>** As the answer, master did "rm -rif" on the programmer's home **
>** directory. And then the C programmer became enlightened... **
>** **
>** Tomasz Rola mailto:tomasz_rola@bigfoot.com **
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGPfreeware 5.0i for non-commercial use
>Charset: noconv
>
>iQA/AwUBQUhX/xETUsyL9vbiEQKAlACg9Rv6rD8INCQFItk1/s5OfZbXjukAn2Mp
>PGjv6ihFXwTInSn8nu3ZOKpu
>=E5XU
>-----END PGP SIGNATURE-----
>
>
>
>
>
>
next prev parent reply other threads:[~2004-09-15 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 12:55 PCI coprocessors Andre Bonin
2004-09-15 12:30 ` Alan Cox
2004-09-15 13:44 ` Matti Aarnio
2004-09-15 13:45 ` Richard B. Johnson
2004-09-15 14:55 ` Tomasz Rola
2004-09-15 15:15 ` Andre Bonin [this message]
2004-09-15 16:49 ` Tonnerre
2004-09-16 0:12 ` Tomasz Rola
2004-09-15 16:01 ` Jeff Garzik
2004-09-15 22:39 ` Tonnerre
2004-09-17 10:16 ` Andre Tomt
2004-09-17 16:19 ` Tony Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41485C7B.40202@bonin.ca \
--to=kernel@bonin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rtomek@cis.com.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox