On Sun, Jun 29, 2003 at 06:44:06PM +0200, Josselin Mouette wrote:
> > Is there any approach that we can avoid publicizing the third party code
> > while porting to Linux? Do we need to write some shim layer code in Linux
> > kernel to interface the third party code? How can we do that? Is there a
Le ven 27/06/2003 à 04:27, G. C. a écrit :
> Dear Sir or Madam,
>
> Currently we are trying to port some third party code to Linux kernel. Some
> modules of third party code need to be ported into Linux kernel and some
> drivers need to be ported from Vxworks to Linux drivers. The problem we hav
On Thu, Jun 26, 2003 at 10:27:40PM -0400, G. C. wrote:
> Currently we are trying to port some third party code to Linux kernel. Some
> modules of third party code need to be ported into Linux kernel and some
> drivers need to be ported from Vxworks to Linux drivers. The problem we
> have is that
"G. C." <[EMAIL PROTECTED]> a tapoté :
> Dear Sir or Madam,
>
> Currently we are trying to port some third party code to Linux
> kernel. Some modules of third party code need to be ported into Linux
> kernel and some drivers need to be ported from Vxworks to Linux
> drivers. The problem we have i
G. C. wrote:
Is there any approach that we can avoid publicizing the third party code
while porting to Linux? Do we need to write some shim layer code in
Linux kernel to interface the third party code? How can we do that? Is
there any document or samples?
In general, this is not possible. It is
Dear Sir or Madam,
Currently we are trying to port some third party code to Linux kernel. Some
modules of third party code need to be ported into Linux kernel and some
drivers need to be ported from Vxworks to Linux drivers. The problem we have
is that this third party does not allow us to publi
6 matches
Mail list logo