linux-kernel - Re: [PATCH 1/2] XCEP PXA255 Processor Board

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] [day] [month] [year] [list]

Date:	Tue, 12 May 2009 17:42:11 +0800
From:	Eric Miao <eric.y.miao@...il.com>
To:	Michael Abbott <michael@...neidae.co.uk>
Cc:	linux-arm-kernel@...ts.arm.linux.org.uk,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] XCEP PXA255 Processor Board

>> > +MACHINE_START(XCEP, "Iskratel XCEP")
>> > +       .phys_io        = 0x80000000,
>> > +       .io_pg_offst    = 0xf8000000,
>> ...... you sure this is correct? Please have a reference to other platforms.
> Now this is very odd.  I've updated these two fields to conform to other
> PXA architectures ... but it looks as if these fields don't actually make
> any difference.  I dug a little, and the only place I could find them
> being used is in arch/arm/kernel/head.S (as MACHINFO_PGOFFIO and _PHYSIO),
> and only there if CONFIG_DEBUG_LL is defined.
>

You are right on this. These are mostly used for the initial mapping
of the IO registers so that low-level debug output like UART output
can work at the very early stage. You will find this very handful if
you are debugging on early bring-up.
--
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/