All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@domain.hid>
To: Sebastian Smolorz <smolorz@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [PATCH] rtcan: add rtcan_plx_pci driver
Date: Tue, 18 May 2010 13:53:24 +0200	[thread overview]
Message-ID: <4BF27FB4.6090301@domain.hid> (raw)
In-Reply-To: <201005181342.57816.smolorz@domain.hid>

Hi Sebastian,

On 05/18/2010 01:42 PM, Sebastian Smolorz wrote:
> Pavel Cheblakov wrote:
>> This is a general driver for cards based on PLX90xx PCI-bridges.
>> It supports following cards:
>>  - Adlink PCI-7841/cPCI-7841 card (http://www.adlinktech.com/)
>>  - Adlink PCI-7841/cPCI-7841 SE card
>>  - esd CAN-PCI/CPCI/PCI104/200 (http://www.esd.eu/)
>>  - esd CAN-PCI/PMC/266
>>  - esd CAN-PCIe/2000
>>  - Marathon CAN-bus-PCI card (http://www.marathon.ru/)
>>  - TEWS TECHNOLOGIES TPMC810 card (http://www.tews.com/)
> 
> The esd cards mentioned above are supported by the RTCAN driver 
> xeno_can_esd_pci. Why do you propose a new driver instead of extending the 
> existing one?

For Socket-CAN, this driver is supposed to support all PLX PCI based
boards including the esd CAN PCI cards and also the IXXAT PCI board (not
yet done, though). The RTCAN driver xeno_can_esd_pci is a *dedicated*
driver for that card without generic support for the PLX PCI chips.
Extending it makes little sense. The question is if we want to drop
xeno_can_esd_pci and xeno_can_ixxat_pci.

Wolfgang.




  reply	other threads:[~2010-05-18 11:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 11:28 [Xenomai-core] [PATCH] rtcan: add rtcan_plx_pci driver Pavel Cheblakov
2010-05-18 11:42 ` Sebastian Smolorz
2010-05-18 11:53   ` Wolfgang Grandegger [this message]
2010-05-18 12:20     ` P.B.Cheblakov
2010-05-18 12:29     ` Sebastian Smolorz
2010-05-18 12:41       ` Wolfgang Grandegger
2010-05-18 13:29         ` Sebastian Smolorz
2010-05-18 13:39           ` Wolfgang Grandegger
2010-05-18 13:45 ` 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=4BF27FB4.6090301@domain.hid \
    --to=wg@domain.hid \
    --cc=smolorz@domain.hid \
    --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.