All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Daniel M. Drucker, Ph.D." <dmd@interactive-motion.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Failing to recognize/use PEAK PCAN-miniPCIe card
Date: Thu, 28 Feb 2013 12:17:14 +0100	[thread overview]
Message-ID: <512F3CBA.6030308@siemens.com> (raw)
In-Reply-To: <CAD1Etoj=9FDB=Zs+qSprpDp9WUkDs6zy6HMy2ctHtekZXOv4Hg@mail.gmail.com>

On 2013-02-28 00:02, Daniel M. Drucker, Ph.D. wrote:
> The latest Linux driver (7.8) from PEAK (
> http://www.peak-system.com/fileadmin/media/linux/files/peak-linux-driver-7.8.tar.gz)
> has the following in its peak_pci_tbl:
> 
> #define PEAK_PCI_DEVICE_ID   0x0001  // ID for PCI / PCIe Slot cards
> #define PEAK_PCIE_CARD_ID    0x0002  // ID for PCIExpress Card
> #define PEAK_PCIE_DEVICE_ID  0x0003  // ID for new PCIe Slot cards
> #define PEAK_CPCI_ID         0x0004  // ID for new cPCI
> #define PEAK_MINIPCI_ID      0x0005  // ID for miniPCI
> #define PEAK_PC104PLUS_ID    0x0006  // ID for new PC-104 Plus
> #define PEAK_PC104E_ID       0x0007  // ID for PC-104 Express
> #define PEAK_MINIPCIE_ID     0x0008  // ID for miniPCIe Slot cards
> 
> 
> Is there any reason why these all shouldn't also be in Xenomai's version?

If those cards are compatible with the ones we already support, you can
go ahead and send a patch to add the IDs to Xenomai's driver. But I
would first cross-check with the kernel commits that added support for
them, if more was changed.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2013-02-28 11:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 19:04 [Xenomai] Failing to recognize/use PEAK PCAN-miniPCIe card Daniel M. Drucker, Ph.D.
2013-02-27 19:25 ` Gilles Chanteperdrix
2013-02-27 19:34   ` Daniel M. Drucker, Ph.D.
2013-02-27 20:08     ` Gilles Chanteperdrix
2013-02-27 20:14       ` Daniel M. Drucker, Ph.D.
2013-02-27 20:15         ` Gilles Chanteperdrix
2013-02-27 20:17           ` Gilles Chanteperdrix
2013-02-27 20:19             ` Daniel M. Drucker, Ph.D.
2013-02-27 21:03               ` Daniel M. Drucker, Ph.D.
2013-02-27 21:08                 ` Gilles Chanteperdrix
2013-02-27 21:12                   ` Daniel M. Drucker, Ph.D.
2013-02-27 23:02                     ` Daniel M. Drucker, Ph.D.
2013-02-28 11:17                       ` Jan Kiszka [this message]
2013-03-02  8:02                       ` Wolfgang Grandegger
2013-02-28 11:26 ` Wolfgang Grandegger

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=512F3CBA.6030308@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=dmd@interactive-motion.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.