netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
Cc: ltp-list <ltp-list@lists.sf.net>,
	Wolfgang Grandegger <wg@grandegger.com>,
	netdev <netdev@vger.kernel.org>
Subject: Re: [LTP] [PATCH v2 0/7] can: CAN network device driver interfaceand  drivers
Date: Thu, 18 Jun 2009 23:01:19 +0530	[thread overview]
Message-ID: <1245346280.5041.30.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <1242125977.5911.40.camel@subratamodak.linux.ibm.com>

Oliver,

You have anything for us now ?

Regards--
Subrata

On Tue, 2009-05-12 at 16:29 +0530, Subrata Modak wrote: 
> Hi Oliver,
> 
> On Tue, 2009-05-12 at 12:46 +0200, Oliver Hartkopp wrote:
> > Wolfgang Grandegger wrote:
> > > Subrata Modak wrote:
> > >> Hi Oliver/Wolfgang,
> > >>
> > >>> Hello,
> > >>>
> > >>> here comes v2 of the patch series posted some time ago. See
> > >>>
> > >>>  http://marc.info/?l=linux-netdev&m=123507025810612&w=4.
> > >>>
> > >>> Changes since v1:
> > > [...]
> > >> Would you also like to send a patch to update the testcases for CAN in LTP
> > >> (http://ltp.cvs.sourceforge.net/viewvc/ltp/ltp/testcases/network/can/filter-tests/) ?
> > >> These tests were originally picked up from:
> > >> http://svn.berlios.de/wsvn/socketcan/trunk/test/?rev=877&sc=1
> > >
> > > The existing tests uses the vcan (virtual CAN) driver, which is not
> > > affected by these patches. Are you thinking about tests using *real* CAN
> > > devices?
> > >
> > 
> > Hi Subrata,
> > 
> > indeed extending the test-cases to the real CAN drivers would urge you 
> > to add a least
> > two hardware CAN-interfaces to your test system and wire them correctly 
> > with the
> > appropriate termination.
> > It's like having *all* ethernet cards available in your linux box to 
> > test them ;-)
> > Some of these CAN controllers are only available as an on-chip device
> > (e.g. for some PowerPC CPUs).
> 
> That makes great sense, as our team uses PowerPC heavily as their test
> hardware.
> 
> I would also like to have tests added to LTP even if i myself do not
> have the hardware to test it. If there´s something of significant
> importance to a group of people/community, for which tests need to
> exist, then they can make into LTP, provided you have tested them and
> Acked them, and somebody else has not complained of any build/run
> breaks.
> 
> > 
> > If there is some room for LTP improvements, i would tend to create some 
> > more test-cases
> > for the networklayer stuff in linux/net/can using the existent virtual 
> > CAN driver.
> 
> Please go ahead.
> 
> Regards--
> Subrata
> 
> > 
> > Best regards,
> > Oliver
> > 
> 
> 
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image 
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list


  reply	other threads:[~2009-06-18 17:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  9:46 [PATCH v2 0/7] can: CAN network device driver interface and drivers Subrata Modak
2009-05-12  9:58 ` Wolfgang Grandegger
2009-05-12 10:46   ` Oliver Hartkopp
2009-05-12 10:59     ` Subrata Modak
2009-06-18 17:31       ` Subrata Modak [this message]
2011-07-10 12:18 ` Update for CAN LTP tests Oliver Hartkopp
2011-07-11 16:15   ` [LTP] " Cyril Hrubis
2011-07-11 17:32     ` CAN: major update for the Controller Area Network " Oliver Hartkopp

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=1245346280.5041.30.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=ltp-list@lists.sf.net \
    --cc=netdev@vger.kernel.org \
    --cc=oliver.hartkopp@volkswagen.de \
    --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).