public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: nejhdeh <nejhdeh@aimedics.com>
To: linux-kernel@vger.kernel.org
Subject: Basic question
Date: Fri, 19 Jul 2002 08:31:55 +1000	[thread overview]
Message-ID: <200207190831.55757.nejhdeh@aimedics.com> (raw)

Hi,

Thanks to your reply erlier. I successfult compiled my device driver separatly 
as module.o and then ran a script to insmod into the kernel.

I have another basic question.

I have two PC systems. First one acts as my development system which I 
develope code using KDevelop running Red Hat linux (2.4.18). When I compile 
my application code (say app.0) and my device driver code (say module.o) then 
I FTP these files into my target system which is a scalled down single-board 
computer (with minimal RAM and disk) which runs linux 2.2.20.

Most of the time everything is O.K. However, when it comes to the device 
driver module (module.o), I get some kernel mismatch problems (obvisouly).

E.g. the file_operations struct in 2.2.20 is different to 2.4.18

My question is: How can I tell gcc or even within the module itself (e.g. 
KERNEL_VERSION) to compile for lower version kernel (i.e tell kernel 2.4.18 
to compile for 2.2.20)

Regards

Nejhdeh Ghevondian


             reply	other threads:[~2002-07-18 22:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18 22:31 nejhdeh [this message]
2002-07-25 12:53 ` Basic question Bill Davidsen
2002-08-23  1:44 ` nejhdeh
  -- strict thread matches above, loose matches on Subject: below --
2002-07-16  1:08 nejhdeh
2002-07-16 12:47 ` Erik Mouw
2001-08-01 20:44 Raghava Raju
2001-08-01 20:55 ` Richard B. Johnson
2001-08-01 21:04 ` Robert Love

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=200207190831.55757.nejhdeh@aimedics.com \
    --to=nejhdeh@aimedics.com \
    --cc=linux-kernel@vger.kernel.org \
    /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