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: <20090615164532.GA7190@huya.quicinc.com>
Date:	Mon, 15 Jun 2009 09:45:32 -0700
From:	davidb@...cinc.com
To:	Pavel Machek <pavel@....cz>
Cc:	Brian Swetland <swetland@...gle.com>, Nicolas Pitre <nico@....org>,
	Ryan Mallon <ryan@...ewatersys.com>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	Tony Lindgren <tony@...mide.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	David Miller <davem@...emloft.net>,
	lkml <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.arm.linux.org.uk" 
	<linux-arm-kernel@...ts.arm.linux.org.uk>
Subject: Re: HTC Dream aka. t-mobile g1 support

On Mon, Jun 15, 2009 at 09:27:46AM -0700, Pavel Machek wrote:

> With right .config file and google's msm tree, running debian is
> fairly easy.
> 
> > The tricky part about something like arm-debian is storage.  You
> > might be able to stick an ext2 on an microSD card, but obviously
> > that's only going to work once the SD driver is functioning.  The
> > phone targets don't generally have ethernet ports on them.
> 
> ext2 on microSD is the key, :-), yes. It boots into multiuser after
> some complains when it tries to access internal NAND (udev?!).

What kind of complaints?  There is some trickiness going on with
the partition table on the NAND, because the CPU running Linux
doesn't have permissions to read the actual partition table.

> The only problem is lack of reasonable keymap. No arrows, no
> escape, no ctrl, no alt, no special symbols... That makes using
> command line very tricky.

Probably related to drivers/char/keyboard.c's

  #warning "Cannot generate rawmode keyboard for your architecture yet."

Does it help to change the change the big block of 'if
defined...' so that CONFIG_ARM isn't dependent on
CONFIG_KEYBOARD_ATKBD?  I'm not sure why that's there, perhaps
there aren't many ARM devices with USB host controllers in them?

David
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ