From: Wolfgang Grandegger <wg@grandegger.com>
To: jprodriguez@elecnor.com, linux-can@vger.kernel.org
Subject: Re: PCH_CAN - echo_skb is occupied
Date: Tue, 01 Apr 2014 21:29:15 +0200 [thread overview]
Message-ID: <533B138B.1010904@grandegger.com> (raw)
In-Reply-To: <CA+vJB=yJ_tF1UwdwpLMVVYMKpTCQCYhWdFGGQNQNn2iP=1V3-A@mail.gmail.com>
On 03/31/2014 11:59 AM, JUAN PEDRO RODRIGUEZ NIETO wrote:
> I am using a Q7 module with Atom processor and EG20T. I am using the
> latest Yocto Dora 10.0.0 to build the embedded linux image. This image
> is still using pch_can.c driver, with the "echo_skb is occupied"
> problem.
>
> I have checked with your post
> http://marc.info/?l=linux-can&m=137180949810229&w=2
> and the source code of pch_can does not have your patch applied.
>
> I am not familiar with kernel patching. Could you please direct me
> where can I find the latest pch_can and how to download your patch in
> patch file format so I can apply it to my poky build?
>
> Is there any plan to release these patches in the master branch?
The EG20T does have a C_CAN core and therefore we would like to switch
to the more advanced C_CAN driver (and get rid of the pch_can driver
sooner than later). It also has less known issues. Last year I posted a
PCH PCI interface driver for the EG20T but it did not make it into
mainline yet. The problem is that I don't have any C_CAN hardware at
hand to validate the patches myself. I'm going to dig the patches out,
end of the week, also for the pch_can.
BTW, what kernel version are you using? Any chance to switch to a recent
mainline kernel?
Wolfgang.
next prev parent reply other threads:[~2014-04-01 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 9:59 PCH_CAN - echo_skb is occupied JUAN PEDRO RODRIGUEZ NIETO
2014-04-01 19:29 ` Wolfgang Grandegger [this message]
2014-04-02 8:35 ` JUAN PEDRO RODRIGUEZ NIETO
2014-04-02 9: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=533B138B.1010904@grandegger.com \
--to=wg@grandegger.com \
--cc=jprodriguez@elecnor.com \
--cc=linux-can@vger.kernel.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.