linux-kernel - Re: [PATCH 04/56] microblaze

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: <4820085B.5010205@seznam.cz>
Date:	Tue, 06 May 2008 09:27:23 +0200
From:	Michal Simek <monstr@...nam.cz>
To:	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>
CC:	linux-kernel@...r.kernel.org, arnd@...db.de,
	linux-arch@...r.kernel.org, John Linn <linnj@...inx.com>,
	john.williams@...alogix.com, matthew@....cx, will.newton@...il.com,
	drepper@...hat.com, microblaze-uclinux@...e.uq.edu.au,
	grant.likely@...retlab.ca, Michal Simek <monstr@...str.eu>
Subject: Re: [PATCH 04/56] microblaze_v2: Open firmware files

In prom.h is it. prom_parse.c of_device.c and of_platform.c will be in drivers/of/

M

> Michal,
> 
> You're missing some of the stuff implemented in powerpc/prom_parse.c, in
> particular this:
> 
> Steve
> 
>> +/**
>> + * of_irq_map_one - Resolve an interrupt for a device
>> + * @device:	the device whose interrupt is to be resolved
>> + * @index:	index of the interrupt to resolve
>> + * @out_irq:	structure of_irq filled by this function
>> + *
>> + * This function resolves an interrupt, walking the tree, for a given
>> + * device-tree node. It's the high level pendant to of_irq_map_raw().
>> + * It also implements the workarounds for OldWolrd Macs.
>> + */
>> +extern int of_irq_map_one(struct device_node *device, int index,
>> +			struct of_irq *out_irq);
>> +
> 
> 
> 
> 
> 
--
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/