public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Bart Hartgers <bart@etpmod.phys.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] (Longhaul 1/5) PCI: Protect bus master DMA from	Longhaul by rw semaphores
Date: Thu, 29 Jun 2006 20:54:15 +0200	[thread overview]
Message-ID: <44A421D7.7050901@interia.pl> (raw)
In-Reply-To: <44A3EEDC.30006@etpmod.phys.tue.nl>

> Maybe you need to do something with the cache bits in CR0 as well. It
> could be something like that. Hardware can be stuborn. I remember the
> old Winchips (C3 predecessors) hanging when trying to disable caching of
> plain ram via MCR's for instance.
> 

I did it like in chapter 10.5.3. Result is exacly the same - processor 
stops. If I set NW flag CPU is still going, but I have "exception in 
interrupt" message.
I'm starting thinking that this will not work for "Nehemiah" core.

Thanks
Rafał


----------------------------------------------------------------------
PS. Fajny portal... >>> http://link.interia.pl/f196a


  parent reply	other threads:[~2006-06-29 18:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 18:25 [PATCH] (Longhaul 1/5) PCI: Protect bus master DMA from Longhaul by rw semaphores Rafał Bilski
2006-06-29 11:37 ` Alan Cox
2006-06-29 12:03   ` Bart Hartgers
2006-06-29 12:50     ` Rafał Bilski
2006-06-29 14:12     ` Rafał Bilski
2006-06-29 15:01       ` Bart Hartgers
2006-06-29 15:40         ` Rafał Bilski
2006-06-30 10:46           ` Bart Hartgers
2006-06-29 15:16       ` Bart Hartgers
2006-06-29 15:55         ` Alan Cox
2006-06-29 18:54         ` Rafał Bilski [this message]
2006-06-29 15:52     ` Alan Cox
     [not found] <fa.lpmuYQxc6OV7Bh11JMM/FzqVWyY@ifi.uio.no>
2006-06-29 23:17 ` Robert Hancock
2006-07-01 18:02   ` Rafał Bilski
  -- strict thread matches above, loose matches on Subject: below --
2006-06-28 13:56 Rafał Bilski
2006-06-28 17:34 ` Greg KH
2006-06-28 18:03   ` Alan Cox
2006-06-28 18:00     ` Jeremy Fitzhardinge
2006-06-28 18:10   ` Dave Jones

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=44A421D7.7050901@interia.pl \
    --to=rafalbilski@interia.pl \
    --cc=bart@etpmod.phys.tue.nl \
    --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