lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3790d380710290605g5d1770fao675418f062f111b9@mail.gmail.com>
Date:	Mon, 29 Oct 2007 14:05:44 +0100
From:	"Wijnand Rietman" <wijnand.rietman@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	wijnand.rietman@...il.com
Subject: CONFIG_IDEDMA_AUTO & 2.4.32 & hdparm -d1

Hello,

I am running Linux on a PC104 board from a compact flash card. Because
the physical DMA lines are missing on some of the compact flash
carrier cards, I would like to be able to boot with DMA disabled and
to enable DMA in a later stage if desired (and supported by hardware).

The problem is that when I set CONFIG_IDEDMA_AUTO to FALSE, I cannot
enable DMA anymore with hdparm, not even with hardware that supports
DMA. If I set CONFIG_IDEDMA_AUTO to TRUE, I can use hdparm to disable
and enable DMA (but of course I get long timeouts with the carrier
cards that do not have the physical DMA lines).

Q1: Is this how the CONFIG_IDEDMA_AUTO setting is supposed to work in
combination with hdparm?
Q2: Is there a way to boot with DMA disabled and to enable it later on
once the system is up and running?

Kernel: 2.4.32
Chipset: CS5530

Any help is highly appreciated!

Regards,
Whinyan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ