linux-kernel - Re: UIO and Fedora 13 (kernel 33.6)

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: <4C7E015B.1010506@steinhoff.de>
Date:	Wed, 01 Sep 2010 09:31:39 +0200
From:	Armin Steinhoff <armin@...inhoff.de>
To:	"Hans J. Koch" <hjk@...utronix.de>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: UIO and Fedora 13  (kernel 33.6)

Small correction ... I don't mean the "initial platform_data" but the 
initial resource data of the platform driver.

--Armin

   Hans J. Koch wrote:
> After a successfull uio_register_device() there is both a /dev/uioX
> and a directory /sys/class/uio/uioX/.

In the attachment is an updated version of uio_jand.

The module uio_jand.ko can be inserted and removed,  no messages visible 
by dmesg, no kernel oops, no dev/uio*  and no class entries available.

There are only entries of uio_jand in /sys/module, 
/sys/bus/platform/drivers and /sys/uio/holders ... I'm really confused =:-/

It's completely unclear how to write the initial platform_data of the 
platform device in the example uio_smx.c :

      regs = platform_get_resource(dev, IORESOURCE_MEM, 0);
      if (!regs) {
          dev_err(&dev->dev, "No memory resource specified\n");
          goto out_free;

Same issue in uio_platform_genirq ...

Cheers

--Armin

View attachment "uio_jand.c" of type "text/x-csrc" (4317 bytes)