Hi,
On Wed, Jul 28, 2010 at 06:44:10PM +0530, Ravi Gupta wrote:
I am new to linux device drivers development. I have created 16 buffers of
size 256 bytes each(using kmalloc()) in my device driver code. I want to
memory map these buffers to user space. Now is it possible to memory map
these
Hi,
since there has been a thread on allowing the use of a coprocessor in
the kernel already: I am wondering if it'd make sense to use AltiVec for
AES in dm-crypt, and how difficult it would be to implement that.
I'm using a PegasosII which has a G4 running at 1 GHz; I get around 3
MB/s
Hi,
'volatile' just doesn't really do what you think it should do. The
PowerPC architecture is too complicated w.r.t. ordering of reads and
writes. In other words, you can't trust it.
It's not sufficient on PowerPC.
It might be necessary, depending on the compiler's mood for moving
Hi,
I just tried upgrading my PegasosII to 2.6.29, and found that the Marvell
driver shows two Ethernet ports now, one with a MAC address ending in
...:de:ad:01 (which is the port that is not wired to the outside), and the
other one with 00:00:00:00:00:00.
I think some sort of Pegasos specific
Hi,
On Tue, Nov 11, 2008 at 11:29:57AM -0600, Matt Sealey wrote:
(the other tool we need is mkimage from U-Boot, I noticed Debian uses this
same command name inside jigdo etc. too, sigh.. also you can't build the
tools without the rest of U-Boot which is hard to envision doing just to
get
Hi,
Arnd Bergmann wrote:
The important part where this connects to the mmc-spi driver is that
you need to set spi_board_info-modalias to mmc-spi, if the
device node can be identified as an mmc card.
Doing that now, using the code you provided as a base. The SPI child
device gets registered,
Hi,
in an embedded system similar to the lite5200 board, there is an MMC
card socket connected to one of the PSCs. Ideally, I'd like to express
this fact via the device tree and have the kernel bind the mmc-spi
driver to the SPI interface, but I cannot find any place where to insert
this code
