public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: miaofng <miaofng@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] CAN console
Date: Mon, 26 Oct 2009 21:53:53 +0800	[thread overview]
Message-ID: <4AE5A9F1.9060002@gmail.com> (raw)
In-Reply-To: <20091026125220.355BD28B9B@gemini.denx.de>

Wolfgang Denk wrote:
>> Is there any chance that the stuff posted by miaofng will be available
>> in u-boot-next?
>>     
>
> I'm not really sure. As Wolfgang Grandegger already commented, the
> implementation is really heavy for a mere boot loader. Sharing code
> with Linux is generally a good thing, but it has to fit, too. I'm not
> convinced it fits here. Let's see wht the now following discussion
> gives. In any case, this is too green for "next". IMHO it would even
> bee too green for "staging" if we had something like this (which we
> don't have :-)
>
>
>   
In fact it's not so heavy, it is  not socket can architecture based!!!
I copied some of linux socket can based  ->driver part<-  of codes and 
added a small wrapped layer(by myself)
only because i am too lazy to rewrite the sja1000 driver.

For blocked or unblocked access problem, it does support both.
To me, i agree mike's view if i write the sja1000 driver from scratch:)

  reply	other threads:[~2009-10-26 13:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  8:20 [U-Boot] CAN console Matthias Weißer
2009-10-26  8:37 ` Mike Frysinger
2009-10-26 11:09   ` Matthias Weißer
2009-10-26 11:26     ` Mike Frysinger
2009-10-26 12:20       ` Matthias Weißer
2009-10-26 12:28         ` Mike Frysinger
2009-10-26 12:52         ` Wolfgang Denk
2009-10-26 13:53           ` miaofng [this message]
2009-10-26 12:28       ` Wolfgang Grandegger
2009-10-26 12:42 ` 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=4AE5A9F1.9060002@gmail.com \
    --to=miaofng@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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