linux-kernel - Re: [tip:x86/doc] x86/doc: mini-howto for using earlyprintk=dbgp

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:	Fri, 06 Mar 2009 08:16:19 -0800
From:	Daniel Walker <dwalker@...o99.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Yinghai Lu <yinghai@...nel.org>, mingo@...hat.com,
	hpa@...or.com, linux-kernel@...r.kernel.org, ebiederm@...ssion.com,
	akpm@...ux-foundation.org, gregkh@...e.de, tglx@...utronix.de,
	sarah.a.sharp@...el.com, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/doc] x86/doc: mini-howto for using earlyprintk=dbgp

On Fri, 2009-03-06 at 16:55 +0100, Ingo Molnar wrote:

> > > 
> > > >From the rest of document I assumed Host/target was referring to both
> > > sides of the connection. So you would need USB on both sides for this
> > > thing to work. I assumed Client/console was just the host. I guess that
> > > is all kind of confusing tho ..
> > 
> > The term "Host" is too confusing to be used here; it has too 
> > many other meanings.  "Target" is good.
> 
> I used Host/Target for that reason, consistently so. The combo 
> gives us the best of both worlds.

What meaning of Host did you intend? Is Host/Target just referring to
one machine in this scenario or both?

> > "Client" is probably okay too, but I don't like "Console" so 
> > much because both machines will have a console.  "Debugging 
> > console" is more accurate but also more cumbersome.
> 
> I used client/console term for that reason.

Same questions for this as above, one machine or both? I think it's
clear from the text when you read it all (not to mention this doesn't
seem like a sophisticated setup), but if someone had trouble with this
they might start reading into the terms and get more confused.

> > > The document indicates you need this one capability on your 
> > > USB port in addition to the USB device (check the complete 
> > > document for how to find the capability). So both host and 
> > > target need this one capability, and then you also need the 
> > > USB device for the whole thing to work.
> > 
> > In fact the original document was rather clear about this; it 
> > says only that the target machine needs the debug capability.  
> > The client machine uses its normal USB driver and treats the 
> > debugging cable as a normal USB serial device.
> 
> yes.
> 
> btw., i think this document is being over-engineered. 
> Significantly so.

I agree (but what are you going to do?)

Daniel

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