All of lore.kernel.org
 help / color / mirror / Atom feed
From: wfp5p@viridian.itc.virginia.edu (Bill Pemberton)
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Mark Hounschell <markh@compro.net>,
	Lidza Louina <lidza.louina@gmail.com>,
	driverdev-devel@linuxdriverproject.org
Subject: Re: [PATCH] Adds Digi driver to staging.
Date: Thu, 18 Jul 2013 14:38:45 -0400	[thread overview]
Message-ID: <20130718183845.8FF0379@viridian.itc.virginia.edu> (raw)
In-Reply-To: <20130718183333.GA19558@kroah.com>

Greg KH writes:
> 
> On Thu, Jul 18, 2013 at 02:25:11PM -0400, Mark Hounschell wrote:
> > On 07/18/2013 01:40 PM, Greg KH wrote:
> > > On Thu, Jul 18, 2013 at 08:26:55AM -0400, Mark Hounschell wrote:
> > >> On 07/17/2013 05:49 PM, Greg KH wrote:
> > >>> On Wed, Jul 17, 2013 at 04:18:01PM -0400, Lidza Louina wrote:
> > >>>> This patch adds the Digi driver to staging.
> > >>>
> > >>> Which digi driver?  For what hardware?  What type of driver is it?
> > >>> Please provide some more details here.
> > >>>
> > >>
> > >>   From the readme:
> > >>
> > >>        This Digi software package includes device drivers for the PCI models
> > >>        of the Digi Neo and ClassicBoard series of products.
> > >>        It is currently supported on the following hardware platforms:
> > >>
> > >>        o Standard i386/i486 and Pentium PC (x86 32bit)
> > >>        o x86 64bit
> > >
> > > I was "hinting" that this needed to be explained in the changelog entry.
> > > The part about the architectures is not needed, as, unless something
> > > really strange is going on in the driver, it should work on all cpus
> > > that support PCI, right?
> > >
> > 
> > That I cannot attest to. The readme also says:
> > 
> >      o Standard i386/i486 and Pentium PC (x86 32bit)
> >       o x86 64bit
> > 
> > I can only personally vouch for Intel/Amd CPUs running in 32 bit mode.
> 
> I'll look at the driver code, but odds are, unless you are assuming a
> specific endian format of some data, all should be fine on other cpu
> types.
> 

If it's anything like dgrp, it will have some places that it assumes a
specific endian format.

-- 
Bill

  reply	other threads:[~2013-07-18 18:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 20:18 [PATCH] Adds Digi driver to staging Lidza Louina
2013-07-17 21:49 ` Greg KH
2013-07-18 12:26   ` Mark Hounschell
2013-07-18 17:40     ` Greg KH
2013-07-18 18:25       ` Mark Hounschell
2013-07-18 18:33         ` Greg KH
2013-07-18 18:38           ` Bill Pemberton [this message]
2013-07-18 20:16             ` Lidza Louina
2013-07-18 20:48             ` Lidza Louina

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=20130718183845.8FF0379@viridian.itc.virginia.edu \
    --to=wfp5p@viridian.itc.virginia.edu \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lidza.louina@gmail.com \
    --cc=markh@compro.net \
    /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.