public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Theodore Bullock <tbullock@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Areca arcmsr kernel integration
Date: Fri, 28 Jul 2006 13:27:49 -0700	[thread overview]
Message-ID: <20060728202749.GA23662@kroah.com> (raw)
In-Reply-To: <25E284CCA9C9A14B89515B116139A94D0C6DF1A4@zrtphxm0.corp.nortel.com>

On Fri, Jul 28, 2006 at 02:07:12PM -0400, Theodore Bullock wrote:
> It would be really nice to see the arcmsr driver integrated into the
> mainline kernel in the nearish future.
> 
> Ideally, the driver would be available before the next major
> distribution is published so that the hardware can be officially
> supported by the distribution developers eg. Novell, Red Hat, Canonical
> ... etc.
> 
> After a brief review of upcoming schedules, Fedora Core looks to be
> updated next in October with the last test release currently scheduled
> for October. After that it will probably be SuSE.
> 
> We have a good number of workstations with this hardware here, but
> support isn't available from our distribution.
> 
> Checking the recent posts it seems that there are two outstanding issues
> 
> > - PAE (cast of dma_addr_t to unsigned long) issues. 
> > - SYNCHRONIZE_CACHE is ignored.  This is wrong.  The sync cache in the
> 
> > shutdown notifier isn't sufficient.
> 
> That said, we have been using an older version of the driver off the
> Areca website for some time now with no major issues (other than kernel
> update problems). 
> 
> Is it possible to get the driver integrated and fix these problems
> after?

Why not fix them up and submit the corrected driver?  If no one wants to
put the effort into fixing these issues now, why would they do the work
later?

thanks,

greg k-h

  reply	other threads:[~2006-07-28 20:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28 18:07 Areca arcmsr kernel integration Theodore Bullock
2006-07-28 20:27 ` Greg KH [this message]
2006-07-29  1:48   ` Bron Gondwana
2006-07-29  2:14     ` Robert Mueller
2006-07-31 21:32       ` Theodore Bullock
2006-08-01  3:03         ` Andrew Morton
2006-08-02 14:53           ` James Bottomley
2006-08-23 23:25             ` Areca arcmsr kernel integration for 2.6.18? Dax Kelson
2006-08-24  0:20               ` Adrian Bunk
2006-08-24  3:42               ` Greg KH
2006-08-24  5:56                 ` Dax Kelson
2006-08-24  8:34                   ` Arjan van de Ven
2006-08-24 11:41                     ` Alan Cox
2006-08-24 16:21                       ` Theodore Bullock
2006-08-24 16:59                         ` Greg KH
2006-08-24  4:11               ` James Bottomley
2006-08-24  6:34                 ` Dax Kelson
2006-09-29  4:11                   ` Bron Gondwana

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=20060728202749.GA23662@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tbullock@nortel.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