linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: s.grosjean@peak-system.com
Cc: Wolfgang Grandegger <wg@grandegger.com>,
	linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: Add support for PEAK PCMCIA PCAN-PC card
Date: Wed, 11 Jan 2012 16:00:25 +0100	[thread overview]
Message-ID: <4F0DA409.4080507@hartkopp.net> (raw)
In-Reply-To: <4F0D9891.6070901@peak-system.com>

On 11.01.2012 15:11, Grosjean Stephane wrote:

>> +config CAN_PEAK_PCMCIA +    tristate "PEAK PCAN PC-CARD Card"
>> 
>> tristate "PEAK PCAN PC-Card (PCMCIA)"
>> 
>> ??
> 
> Please confirm: you'd like me to add the "(PCMCIA)" string at the end of
> the menu text, wouldn't you?



I read some more Kconfigs to check the current handling in other drivers.

I think

	tristate "PEAK PCAN PC-Card"

is better - and reflects the PEAK adapter name (note the upper/lower case!).
Although the Kconfig entry is only visible when PCMCIA is enabled.

> 
>> Should we probably put all PCMCIA cards into a separate
>> 
>> linux/drivers/net/can/sja1000/pcmcia
>> 
>> directory - like we have it for the USB devices?
> 
> If my Humble Opinion may help you: not sure this will be lots of other
> pcmcia (can) adapters in the future...


ok. Forget it :-)

>>>> +    depends on PCMCIA +    ---help--- +      This driver is for the
>>>> PCAN PC-CARD PCMCIA card with 1 or 2 channels +      from PEAK
>>>> Systems (http://www.peak-system.com). +


(..)

>>>> +obj-$(CONFIG_CAN_PEAK_PCMCIA) += peak_pcmcia.o
>> 
>> This should be the module/driver name too.
>>>> + +/* PEAK-System PCMCIA driver name */ +#define DRV_NAME
>>>> "peak_pccard"
>>> I find the mix of "peak_pcmcia" and "peak_pccard" and "pcan_pccard"
>>> for the same hardware confusing. Please use just one name and prefix.
>> 
>> Yep - peak_pcmcia
> 
> We just finished to talk about that and, as far as the PCAN-PC Card is a 
> PC-CARD (16bit), we'd like to use the "peak_pccard" text for the
> module/module file/source file names instead of "peak_pcmcia". Related
> question: I suppose I'll have to change the "CONFIG_CAN_PEAK_PCMCIA" into
> "CONFIG_CAN_PEAK_PCCARD" too. Please confirm.


Hm. Not that good IMO ...

If you look into the Kernel config options there's a difference between PCCARD
and PCMCIA:

linux/drivers/pcmcia/Kconfig says

---8<--- snip

if PCCARD

config PCMCIA
        tristate "16-bit PCMCIA support"
        select CRC32
        default y
        ---help---
           This option enables support for 16-bit PCMCIA cards. Most older
           PC-cards are such 16-bit PCMCIA cards, so unless you know you're
           only using 32-bit CardBus cards, say Y or M here.

           To use 16-bit PCMCIA cards, you will need supporting software in
           most cases. (see the file <file:Documentation/Changes> for
           location and details).

           To compile this driver as modules, choose M here: the
           module will be called pcmcia.

           If unsure, say Y.

---8<--- snip

So your hardware is not a 32-bit Cardbus but a 16-bit PCMCIA card.

Putting the "PCAN-PC card" into the Kconfig description is fine but the driver
source and kernel module should reflect the (16 bit) pcmcia driver state.

You may add to your Kconfig entry:

           To compile this driver as module, choose M here: the
           module will be called peak_pcmcia.


Regards,
Oliver


  parent reply	other threads:[~2012-01-11 15:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 14:51 Add support for PEAK PCMCIA PCAN-PC card Stephane Grosjean
2012-01-09 23:23 ` Marc Kleine-Budde
2012-01-11 15:13   ` Grosjean Stephane
2012-01-10 13:41 ` Wolfgang Grandegger
2012-01-10 15:05   ` Oliver Hartkopp
2012-01-11 14:11     ` Grosjean Stephane
2012-01-11 14:43       ` Wolfgang Grandegger
2012-01-11 15:00       ` Oliver Hartkopp [this message]
2012-01-11 15:11         ` Wolfgang Grandegger
2012-01-11 17:10   ` Grosjean Stephane
2012-01-11 18:35     ` 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=4F0DA409.4080507@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=linux-can@vger.kernel.org \
    --cc=s.grosjean@peak-system.com \
    --cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).