All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Don Newbold <d.o.newbold@gmail.com>, xenomai@xenomai.org
Subject: Re: driver make files and target architecture size
Date: Tue, 12 Feb 2019 09:20:40 +0100	[thread overview]
Message-ID: <31b61932-40c0-2719-24ee-6be9d8a2520d@xenomai.org> (raw)
In-Reply-To: <ba52d8a1-4012-dbd9-6d34-e10d0237cd35@gmail.com>

On 2/12/19 5:25 AM, Don Newbold via Xenomai wrote:
> Hi all,
> 
> This is my first post, so please excuse my shortcomings.
> 
> I've been writing and maintaining Linux drivers for over 15 years, and
> am now being tasked with Xenomai support.
> 
> 1. When I look at the driver make files included with the latest Xenomai
> download they look totally foreign. Is the existing Linux driver module
> makefile format usable or must another format be generated?

Xenomai uses regular Makefiles for the kernel bits it provides. It also
uses autoconf-generated Makefiles for the userland components. E.g.
kernel/cobalt/Makefile describes the build recipe for the Xenomai core
in a way that should be familiar to you. This makefile and the related
sources are introduced into a regular kernel tree by a script called
"prepare-kernel.sh".

You may find detailed information there:
https://gitlab.denx.de/Xenomai/xenomai/wikis/Installing_Xenomai_3

> 
> 2. I'm familiar with building drivers to support 32-bit vs 64-bit
> targets. I see that Xenomai has in the past had x64 support, but I now
> only see x86. Please clarify the current x86 vs x64 support.
> 

kernel/cobalt/arch/x86 includes both 32 and 64 bit support.

-- 
Philippe.


  reply	other threads:[~2019-02-12  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12  4:25 driver make files and target architecture size Don Newbold
2019-02-12  8:20 ` Philippe Gerum [this message]
2019-02-12 10:03   ` Jan Kiszka

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=31b61932-40c0-2719-24ee-6be9d8a2520d@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=d.o.newbold@gmail.com \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.