public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Gerhard Pircher" <gerhard_pircher@gmx•net>
To: Marcus Comstedt <marcus@mc•pp.se>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] EHCI Oops on CONFIG_NOT_COHERENT_CACHE system
Date: Wed, 30 Aug 2006 11:01:43 +0200	[thread overview]
Message-ID: <20060830090143.44170@gmx.net> (raw)
In-Reply-To: <yf9mz9np82b.fsf@omoikane.mc.pp.se>


-------- Original-Nachricht --------
Datum: Tue, 29 Aug 2006 23:04:44 +0200
Von: Marcus Comstedt <marcus@mc•pp.se>
An: "Gerhard Pircher" <gerhard_pircher@gmx•net>
Betreff: Re: [PATCH] EHCI Oops on CONFIG_NOT_COHERENT_CACHE system

> 
> "Gerhard Pircher" <gerhard_pircher@gmx•net> writes:
> 
> > Hi Marcus,
> >
> > I guess this message should also be forwarded to
> > linux-usb-devel@lists•sourceforge.net. I hope the developers there can
> > make some comments.
> >
> > Gerhard
> 
> 
> Well, I figured the first thing to do would be to reach a consensus
> here on whether or not atomic_t:s in DMA memory should be ruled as
> unallowed.  Judging from the massive silence, there doesn't seem to be
> any strong opinions either way though...
> 
> 
>   // Marcus
> 

You're right. Maybe it's a topic for the linuxppc-embedded mailing list, because mostly embedded platforms use the CONFIG_NOT_COHERENT_CACHE option.

Gerhard

-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

  reply	other threads:[~2006-08-30  9:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-27 16:17 [PATCH] EHCI Oops on CONFIG_NOT_COHERENT_CACHE system Marcus Comstedt
2006-08-29 15:07 ` Gerhard Pircher
2006-08-29 21:04   ` Marcus Comstedt
2006-08-30  9:01     ` Gerhard Pircher [this message]
     [not found] <9mz9np82b.fsf@omoikane.mc.pp.se>
2006-08-30 14:24 ` Milton Miller
2006-08-30 17:42   ` Marcus Comstedt

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=20060830090143.44170@gmx.net \
    --to=gerhard_pircher@gmx$(echo .)net \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=marcus@mc$(echo .)pp.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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