netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org
Cc: Socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH net-next-2.6 v2 1/1] can: c_can: Added support for Bosch C_CAN controller
Date: Thu, 16 Dec 2010 10:31:56 -0800 (PST)	[thread overview]
Message-ID: <20101216.103156.104072504.davem@davemloft.net> (raw)
In-Reply-To: <4D0A5236.5070900-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>

From: Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
Date: Thu, 16 Dec 2010 18:53:58 +0100

> On 12/16/2010 01:09 PM, Tomoya MORINAGA wrote:
>> On Thursday, December 16, 2010 6:11 PM, Wolfgang Grandegger wrote:
>> 
>>> Ah, oh, I just realized that the register layout is almost identical to
>>> the recently accepted *pch_can* driver. Tomoya, does pch_can use a c_can
>>> core? Well, then it makes really sense to have a generic c_can driver
>>> for the SPEAR, PCH, etc. Board specific details are handled via platform
>>> definition. This driver already provides that functionality, IFAICS.
>> 
>> Hi Wolfgang,
>> 
>> It seems pch_can similar to c_can.
>> However, sorry, I don't know if pch_can core is the same as c_can since
>> LSI is provided by Intel.
>> If necessary, please contact to Intel.
> 
> You could also try to use that driver. I'm rather sure that it does work
> on your hardware as well.

Indeed.

  parent reply	other threads:[~2010-12-16 18:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15  9:58 [PATCH net-next-2.6 v2 1/1] can: c_can: Added support for Bosch C_CAN controller Bhupesh Sharma
     [not found] ` <1292407130-19791-1-git-send-email-bhupesh.sharma-qxv4g6HH51o@public.gmane.org>
2010-12-16  9:11   ` Wolfgang Grandegger
2010-12-16 12:09     ` Tomoya MORINAGA
     [not found]       ` <070E08D3134344CBB04FC2F201E778B7-c0cKtqp5df7I9507bXv2FdBPR1lH4CV8@public.gmane.org>
2010-12-16 17:53         ` Wolfgang Grandegger
     [not found]           ` <4D0A5236.5070900-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2010-12-16 18:31             ` David Miller [this message]
2010-12-17 21:21   ` Wolfgang Grandegger
     [not found]     ` <4D0BD454.3060503-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2010-12-20  4:29       ` Bhupesh SHARMA
     [not found]         ` <D5ECB3C7A6F99444980976A8C6D896384DEAE47E1A-8vAmw3ZAcdzhJTuQ9jeba9BPR1lH4CV8@public.gmane.org>
2010-12-20 20:39           ` Wolfgang Grandegger
     [not found]             ` <4D0FBEF6.8020207-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2010-12-21  4:48               ` Bhupesh SHARMA
     [not found]                 ` <D5ECB3C7A6F99444980976A8C6D896384DEAE481B6-8vAmw3ZAcdzhJTuQ9jeba9BPR1lH4CV8@public.gmane.org>
2010-12-21 19:27                   ` Wolfgang Grandegger
     [not found]                     ` <4D10FF97.1070703-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2010-12-22  3:36                       ` Bhupesh SHARMA
     [not found]                         ` <D5ECB3C7A6F99444980976A8C6D896384DEAE48416-8vAmw3ZAcdzhJTuQ9jeba9BPR1lH4CV8@public.gmane.org>
2010-12-22  6:52                           ` Marc Kleine-Budde
     [not found]                             ` <4D11A039.5090006-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-12-22  7:50                               ` Wolfgang Grandegger
     [not found]                                 ` <4D11ADD2.40506-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2010-12-22  8:03                                   ` Bhupesh SHARMA
     [not found]                                     ` <D5ECB3C7A6F99444980976A8C6D896384DEAE4855F-8vAmw3ZAcdzhJTuQ9jeba9BPR1lH4CV8@public.gmane.org>
2010-12-22  8:10                                       ` Wolfgang Grandegger
2010-12-17 21:33   ` Marc Kleine-Budde
     [not found]     ` <4D0BD744.5030609-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-12-17 21:45       ` Wolfgang Grandegger
2010-12-20  4:37       ` Bhupesh SHARMA

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=20101216.103156.104072504.davem@davemloft.net \
    --to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
    --cc=Socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).