Hi,
I'm trying to enable the MEI on my graphics card, to allow for firmware
updates. The MEI is enumerated through an auxiliary bus, so it is
detected only when the main driver is loaded.
The MEI driver tries to register an interrupt. On PPC64 (LE), I get:
xe 0030:03:00.0: enabling device (0
Hi,
On 8/5/25 13:58, Eric Biggers wrote:
What does this have to do with this thread, which is about the PowerPC
optimized MD5 code?
Hence the new subject. It is still related to removal of code, but asks
about the bigger picture.
The code removal changes you've been pushing lately absolute
Hi,
On 8/5/25 07:59, Eric Biggers wrote:
md5sum uses the kernel's MD5 code:
What? That's crazy. Userspace MD5 code would be faster and more
reliable. No need to make syscalls, transfer data to and from the
kernel, have an external dependency, etc. Is this the coreutils md5sum?
We need to
Hi,
On 8/4/25 05:44, Eric Biggers wrote:
Taken together, it's clear that it's time to retire these additional MD5
implementations, and focus maintenance on the MD5 generic C code.
[...]
- ldd [%o1 + 0x00], %f8
- ldd [%o1 + 0x08], %f10
- ldd [%o1 + 0x10], %f12
-
Hi,
I have two lines starting with "LOC:" in /proc/interrupts, one with a
comment "Local timer interrupts for timer event device", the other
"Local timer interrupts for others".
This makes collectd unhappy, because it uses the first column as a
unique identifier.
Is this column supposed to
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
> thes
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 throughpu
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 f
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 ha
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 regist
Hi,
Robert Schwebel wrote:
> Or is your question how to express this in the device tree?
This. As far as I can see, using the device tree for this is currently
unsupported, and everyone who uses the mmc-spi driver just creates a
platform device in the board startup code, which strikes me as so
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
13 matches
Mail list logo
