linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mattias Boström" <mattias.bostroem@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Patches for Peak CAN driver for MPC5200B?
Date: Tue, 29 Jan 2008 17:48:35 +0100	[thread overview]
Message-ID: <10d674cb0801290848p8cd6d1xdf03e793e6de58a1@mail.gmail.com> (raw)

Hi,

We are using peak-linux-driver-3.17 with patches from DENX (mpc5200)
and Freescale (mpc5200-platform_driver) on a MPC5200B. We have
problems with rmmod, resulting in kernel panic. We also have a problem
with not detecting BusOff. Does anyone know of additional patches that
solve these problems?
If we solve it ourselfs, would this be a good place to post patches?

Regards,
Mattias

             reply	other threads:[~2008-01-29 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 16:48 Mattias Boström [this message]
2008-01-29 19:17 ` Patches for Peak CAN driver for MPC5200B? Grant Likely
2008-01-29 19:50 ` 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=10d674cb0801290848p8cd6d1xdf03e793e6de58a1@mail.gmail.com \
    --to=mattias.bostroem@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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).