public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Thorsten Glaser <tg@debian.org>
Cc: linux-m68k@vger.kernel.org
Subject: Re: [PATCH 1/1] m68k: add missing I/O macros {in,out}{w,l}_p() for !CONFIG_ISA
Date: Mon, 4 Oct 2010 21:51:21 +1100 (EST)	[thread overview]
Message-ID: <alpine.OSX.2.00.1010042123060.285@localhost> (raw)
In-Reply-To: <Pine.BSM.4.64L.1010041016060.29280@herc.mirbsd.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1283 bytes --]


On Mon, 4 Oct 2010, Thorsten Glaser wrote:

> Finn Thain dixit:
> 
> Besides, this seems like a simple fix or an accidental omission to me. 
> What is with all this bikeshedding?

It isn't bikeshedding. Recall that I built these sources a few weeks ago 
when you mentioned the speakup issue in private correspondence. At the 
time, I built speakup in 2.6.32-23 to see if it would behave differently 
than the 2.6.3[45] sources that were giving you grief.

It built for me at the time, so I was suprised to find out it didn't build 
for you, and naturally I wanted to know what I did wrong.

It may be that speakup works on amiga and atari (I don't know). It doesn't 
work on mac as there are no audio drivers. It has long frustrated me that 
there is bloat in the debian kernel configs. So perhaps I am guilty of 
being unfairly obstructionist here, in the hope that the config file 
issues could be addressed. My apologies.

> Some macros are not available on m68k if CONFIG_ISA is not set, but they 
> are available “almost” or even really everywhere else, so drivers use 
> them, so m68k is buggy in not providing them. (Outsider’s PoV.)

You may be right. I confess to being ignorant when it comes to ISA.

Finn

> 
> bye,
> //mirabilos
> 

  reply	other threads:[~2010-10-04 10:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03 18:38 [PATCH 0/1] m68k: add missing I/O macros {in,out}{w,l}_p() for !CONFIG_ISA Thorsten Glaser
2010-10-03 18:48 ` [PATCH 1/1] " Thorsten Glaser
2010-10-04  0:51   ` Finn Thain
2010-10-04  7:40     ` Thorsten Glaser
2010-10-04  8:47       ` Finn Thain
2010-10-04  9:10         ` Thorsten Glaser
2010-10-04 10:22           ` Finn Thain
2010-10-04 11:30             ` Thorsten Glaser
2010-10-04 13:18             ` Geert Uytterhoeven
2010-10-04 13:33               ` Finn Thain
2010-10-04 13:40               ` Thorsten Glaser
2010-10-04 14:01                 ` Geert Uytterhoeven
2010-10-04 14:13                   ` Thorsten Glaser
2010-10-04 19:20                   ` Thorsten Glaser
2010-10-13 20:17                   ` Thorsten Glaser
2010-10-05 12:56                 ` Stephen R. Marenka
2010-10-05 14:10                   ` debian kernel config, was " Finn Thain
2010-10-06  0:57                   ` Stephen R. Marenka
2010-10-06  9:26                   ` Thorsten Glaser
2010-10-06 13:09                     ` Stephen R. Marenka
2010-10-06 14:15                     ` Finn Thain
2010-10-04  7:57   ` Michael Schmitz
2010-10-04  8:13     ` Thorsten Glaser
2010-10-04  9:08       ` Finn Thain
2010-10-04 10:18         ` Thorsten Glaser
2010-10-04 10:51           ` Finn Thain [this message]
2010-10-04 11:37             ` Thorsten Glaser
2010-10-04 12:45               ` Finn Thain
2010-10-16 17:12   ` Geert Uytterhoeven

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.OSX.2.00.1010042123060.285@localhost \
    --to=fthain@telegraphics.com.au \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@debian.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