public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Dimitris Zilaskos <dzila@tassadar.physics.auth.gr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: promise 20268 dma lockups with 2.4 & 2.6
Date: Sat, 06 May 2006 04:08:35 +0200	[thread overview]
Message-ID: <1146881315.3026.2.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0604301535500.1829@tassadar.physics.auth.gr>

this seems to be a problem with promise ultra 133 TX2 aswell.. i tried
contacting promise, and the people listed in the driver file, no
response... i have myself pretty much given up on getting this solved. i
dont have the nessecary expertise myself, and i cant get in touch with
those who do.. this has also been posted to lkml before..

<snip>
> 
>  	Any help is appreciated.
> 
>  	Best regards,
> 
> --
> ============================================================================
> 
> Dimitris Zilaskos
> 
> Department of Physics @ Aristotle University of Thessaloniki , Greece
> PGP key : http://tassadar.physics.auth.gr/~dzila/pgp_public_key.asc
>  	  http://egnatia.ee.auth.gr/~dzila/pgp_public_key.asc
> MD5sum  : de2bd8f73d545f0e4caf3096894ad83f  pgp_public_key.asc
> ============================================================================
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2006-05-06  2:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-30 13:23 promise 20268 dma lockups with 2.4 & 2.6 Dimitris Zilaskos
2006-05-06  2:08 ` Kasper Sandberg [this message]
2006-05-06  9:06   ` Dimitris Zilaskos
2006-06-01 17:00   ` Alan Cox

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=1146881315.3026.2.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=dzila@tassadar.physics.auth.gr \
    --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