linux-kernel - Re: Problem with /proc/iomem on ARM

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: <ac3eb2510907011112k690e5c38y2a8871dde5db1f13@mail.gmail.com>
Date:	Wed, 1 Jul 2009 20:12:38 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	H Hartley Sweeten <hartleys@...ionengravers.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Problem with /proc/iomem on ARM

On Wed, Jul 1, 2009 at 20:01, H Hartley
Sweeten<hartleys@...ionengravers.com> wrote:

> The serial ports on my system are amba bus devices.
>
>> After all, it seems like this should be fixed in arm somewhere, not to
>> copy and store internal driver core pointers, but use the device
>> itself to retrieve the values.
>
> Maybe the problem is in drivers/amba/bus.c? amba_device_register() does:
>
>        dev->res.name = dev_name(&dev->dev);

Looks like. If you get the name directly from dev->init_name. Does that work?

Thanks,
Kay
--
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/