mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Christoph Hellwig <hch@lst.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-alpha@vger.kernel.org
Subject: Re: is alpha jensen support dead?
Date: Sun, 21 May 2017 14:18:40 +0300 (EEST)	[thread overview]
Message-ID: <alpine.LRH.2.20.1705211414440.27352@math.ut.ee> (raw)
In-Reply-To: <20170521105032.5F0807FF0E@ilves.cyber.ee>

> Hi all,
> 
> it seems like the Alpha Jense build (the only one using pci-noop.c)
> and thus being a different build than all the later PCI capable
> system has been broken since at least:
> 
> commit 6aca0503847f6329460b15b3ab2b0e30bb752793
> Author: Christian Borntraeger <borntraeger@de.ibm.com>
> Date:   Tue Feb 2 21:46:33 2016 -0800
> 
>     alpha/dma: use common noop dma ops
> 
> which switches pci-noop.c to use generic code, but fat fingered a symbol
> and didn't wire up the Kconfig.
> 
> Is there any value in keeping it alive?  Especially as there probably
> isn't any build coverage..

I do not have any experience with Jensens.

> Btw, how well is alpha working these days?  It looks like there hasn't
> been any maintainer activity for about two years.

However, I keep PC164, DS10, DS10L, DS20 alive and plan to revice 
my XP1000 too. A 21264-base half embedded system worked fine until I 
broke a connector on it so hoping to revive it too.

PC164, DS10, DS10L worked fine with 4.1 for me, others are on earlier 
kernels.

-- 
Meelis Roos (mroos@linux.ee)

       reply	other threads:[~2017-05-21 11:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170521105032.5F0807FF0E@ilves.cyber.ee>
2017-05-21 11:18 ` Meelis Roos [this message]
2017-05-21  8:58 Christoph Hellwig
2017-05-21 18:11 ` Bob Tracy
2017-05-22  7:51   ` Christoph Hellwig
2017-06-05 12:49     ` Maciej W. Rozycki
2017-05-22  5:33 ` Matt Turner
2017-05-22  5:50 ` Michael Ellerman
2017-05-24  9:16 ` Christian Borntraeger
2017-05-24  9:30   ` Christoph Hellwig

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=alpine.LRH.2.20.1705211414440.27352@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=hch@lst.de \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome