On Fri, Nov 06, 2020 at 01:52:01PM +1100, Finn Thain wrote:
> On Fri, 23 Oct 2020, Geert Uytterhoeven wrote:
>
> > > > > The arm/rpc timer seems to be roughly in the same category as most
> > > > > of the m68k ones or the i8253 counter on a PC. It's possible that
> > > > > some of them could
Acked-by: Sam Creasey
On Wed, Jul 02, 2014 at 09:41:33PM -0400, Nicholas Krause wrote:
> Removes a FIXME comment in this file due to it not compiling
> as it now compiles.
>
> Signed-off-by: Nicholas Krause
> ---
> arch/m68k/include/asm/sun3_pgalloc.h | 1 -
> 1 fil
Acked-by: Sam Creasey sa...@sammy.net
On Wed, Jul 02, 2014 at 09:41:33PM -0400, Nicholas Krause wrote:
Removes a FIXME comment in this file due to it not compiling
as it now compiles.
Signed-off-by: Nicholas Krause xerofo...@gmail.com
---
arch/m68k/include/asm/sun3_pgalloc.h | 1 -
1
Acked-by: Sam Creasey
On Wed, Mar 19, 2014 at 11:35:16PM +1100, Finn Thain wrote:
>
> This patch series addresses several issues with NCR5380 drivers:
>
> 1. The complex network of #include directives.
>
> 2. Three inconsistent implementations of the core driver all attemp
Acked-by: Sam Creasey sa...@sammy.net
On Wed, Mar 19, 2014 at 11:35:16PM +1100, Finn Thain wrote:
This patch series addresses several issues with NCR5380 drivers:
1. The complex network of #include directives.
2. Three inconsistent implementations of the core driver all attempting
On Mon, Feb 05, 2007 at 10:13:21PM +0300, Cyrill V. Gorcunov wrote:
> This patch adds checking for allocated DVMA
> memory and granted IRQ line.
>
> Signed-off-by: Cyrill V. Gorcunov <[EMAIL PROTECTED]>
Acked-by: Sam Creasey <[EMAIL PROTECTED]>
Included in my tree fo
On Mon, Feb 05, 2007 at 10:13:21PM +0300, Cyrill V. Gorcunov wrote:
This patch adds checking for allocated DVMA
memory and granted IRQ line.
Signed-off-by: Cyrill V. Gorcunov [EMAIL PROTECTED]
Acked-by: Sam Creasey [EMAIL PROTECTED]
Included in my tree for rolling back into m68k. I'm fine
On Thu, 25 Aug 2005, Al Viro wrote:
> On Thu, Aug 25, 2005 at 09:59:05AM -0400, Sam Creasey wrote:
>
> > I have been a little out of it for a while on the sun3 stuffs, I'll admit
> > (cursed day job), but I really, really intend to get recent 2.6 running
> > again
On Thu, 25 Aug 2005, Geert Uytterhoeven wrote:
> Can't you use the plain m68k toolchain? I always used a m68k-linux-gcc 3.3.3
> for my uClinux experiments.
>
> > sun3 is seriously broken and I doubt that we'll see any takers for testing
> > 2.6 on those anyway ;-)
Hey, I'm writing this on a
On Thu, 25 Aug 2005, Geert Uytterhoeven wrote:
Can't you use the plain m68k toolchain? I always used a m68k-linux-gcc 3.3.3
for my uClinux experiments.
sun3 is seriously broken and I doubt that we'll see any takers for testing
2.6 on those anyway ;-)
Hey, I'm writing this on a sun3! :)
On Thu, 25 Aug 2005, Al Viro wrote:
On Thu, Aug 25, 2005 at 09:59:05AM -0400, Sam Creasey wrote:
I have been a little out of it for a while on the sun3 stuffs, I'll admit
(cursed day job), but I really, really intend to get recent 2.6 running
again. Knowing that the rest of m68k
On Thu, 21 Apr 2005, Christoph Hellwig wrote:
> On Thu, Apr 21, 2005 at 11:58:12AM +0200, Geert Uytterhoeven wrote:
> > sun3_NCR5380.c still uses the following:
> >
> > - SCSI_ABORT_SUCCESS
> > - SCSI_ABORT_ERROR
> > - SCSI_ABORT_SNOOZE
> > - SCSI_ABORT_BUSY
> > -
On Thu, 21 Apr 2005, Christoph Hellwig wrote:
On Thu, Apr 21, 2005 at 11:58:12AM +0200, Geert Uytterhoeven wrote:
sun3_NCR5380.c still uses the following:
- SCSI_ABORT_SUCCESS
- SCSI_ABORT_ERROR
- SCSI_ABORT_SNOOZE
- SCSI_ABORT_BUSY
- SCSI_ABORT_NOT_RUNNING
-
13 matches
Mail list logo
