linux-kernel - Re: Setting up Silicon image 3114 in DMA mode

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C257E67.9090101@gmail.com>
Date:	Fri, 25 Jun 2010 22:13:27 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	amruth pattanada <amruth.vamadev@...il.com>
CC:	linux-ide@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Setting up Silicon image 3114 in DMA mode

On 06/25/2010 02:25 AM, amruth pattanada wrote:
> Hi
> Can anybody please guide me what minimal steps to follow for setting
> up 3114 for operating in DMA mode and looked into linux 2.6.32.7 code.
> I am porting 3114 driver to RTOS but have problems in using BAR5 PCI
> config space because of Memory mapped region issues. I can access BAR4
> and plan to set up DMA mode.
> How do we access entire BAR5 memory space without using BAR5, is there
> any indirect way to access BAR5 using BAR4. Please let me know.
> Thanks
> Amruth p.v
> Sr.Embedded Engineer

See the datasheet (PCI Configuration Space section), there's a way to 
access BAR5 registers using indirect access registers in configuration 
space. I expect this will be relatively slow, however.
--
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/