public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: "Hen, Shmulik" <shmulik.hen@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Developing code for ia64
Date: Mon, 10 Sep 2001 12:53:18 +0100	[thread overview]
Message-ID: <3B9CA9AE.DE0BD28F@redhat.com> (raw)
In-Reply-To: <07E6E3B8C072D211AC4100A0C9C5758302B27313@hasmsx52.iil.intel.com>

"Hen, Shmulik" wrote:
> 
> Hi,
> 
> When developing kernel drivers (module) for ia64, is it necessary to do it
> on an ia64 machine ?
> Our product contains a pre-compiled core object (IP protection :-\ ) and a
> set of wrapper source files, so for dual platform support the tar ball has
> to contain both an ia32 and ia64 versions of the executable. Is there any
> way to get an ia64 compiler (and libs) installed on an ia32 machine and use
> it to get ia64 compatible binaries ?

I would seriously recommend to intel to consider NOT doing this. Binary
only modules 
are generally frowned upon and there is (almost) never a good reason for
doing
them. If you're concerned about firmware, that's a totally different
issue,
binary firmware images can be done in a much simpler way.

But PLEASE don't do such a binary only module; I thought Intel was more 
Open Source friendly than that. (And I know most parts of Intel are; the
CPU folks and the networking folks are VERY helpful)

For one, almost no Linux distribution will ship with your drivers so
customers 
have go to a lot of hassle to compile their own drivers, and by doing
that
they loose all support from the community.

Greetings,
   Arjan van de Ven

  reply	other threads:[~2001-09-10 11:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10 11:17 Developing code for ia64 Hen, Shmulik
2001-09-10 11:53 ` Arjan van de Ven [this message]
2001-09-10 12:02 ` David Woodhouse
2001-09-10 12:57 ` Rik van Riel
     [not found]   ` <Pine.LNX.4.33L.0109100956181.20670-100000@duckman.distro.conect iva>
2001-09-10 17:49     ` Alex Bligh - linux-kernel
2001-09-10 13:35 ` Alan Cox
2001-09-10 22:51 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2001-09-10 15:08 Hen, Shmulik

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=3B9CA9AE.DE0BD28F@redhat.com \
    --to=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shmulik.hen@intel.com \
    /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