Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[PATCH] nforce2 dma enabled

0 views
Skip to first unread message

Tim Krieglstein

unread,
Dec 12, 2002, 9:20:09 AM12/12/02
to
Hi
I just got a new toy an epox EP-8RDA. Since there is an nforce2 chipset
onboard and only support for the nforce (whithout 2) in the 2.4.20-ac2
kernel. I just concluded that the new ide driver should be pretty
similar to the old one. i had absolutly no documentation! so be
careful! Personally i did an full backup *before* fiddling with the ide
driver :)

The patch just adds the pci id of the nforce ide controller and added a
new information block to the ide_pci_device_t structure. Also i added an
entry to pci_device_id.

This is my first public patch so suggestions or other feedback is very
welcome. I would also like to know why the lspci command still tells me
this is an unknown device after applying my patch seen below. Also if
someone has a hint why the usb-devices have no interrupt assigned and
thus are not available is very welcome (probably disable acpi?).

However currently i am runing with following settings enabled (by hand):
/dev/hda:
multcount = 16 (on)
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 1 (on)
readonly = 0 (off)
readahead = 8 (on)
geometry = 15505/240/63, sectors = 234441648, start = 0

Have fun
Tim

PS: Please CC me since im am currently not subscribed to the list

nforce2.patch

Alan Cox

unread,
Dec 12, 2002, 1:40:08 PM12/12/02
to
On Thu, 2002-12-12 at 14:06, Tim Krieglstein wrote:
> The patch just adds the pci id of the nforce ide controller and added a
> new information block to the ide_pci_device_t structure. Also i added an
> entry to pci_device_id.

Thanks.

> welcome. I would also like to know why the lspci command still tells me
> this is an unknown device after applying my patch seen below. Also if

lspci uses its own tables in user space

> someone has a hint why the usb-devices have no interrupt assigned and
> thus are not available is very welcome (probably disable acpi?).

The BIOS didnt assign one. Since we don't have any useful docs we also
can't reassign one unless the BIOS does it - which it might do.


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

0 new messages