From: Sicelo <absicsz@gmail.com>
To: Ashish Shah <ashish@emailuser.net>
Cc: "Pali Rohár" <pali@kernel.org>,
maemo-leste@lists.dyne.org, u-boot@lists.denx.de
Subject: Re: [maemo-leste] Broken u-boot on n900 hw (possibly CONFIG_POSITION_INDEPENDENT)
Date: Sat, 19 Nov 2022 20:24:47 +0200 [thread overview]
Message-ID: <Y3kfbxO8HzBAVlou@tp440p.steeds.sam> (raw)
In-Reply-To: <3b627d0a-13a7-4cc3-889d-f03782771a33@app.fastmail.com>
On Sat, Nov 19, 2022 at 08:38:33AM -0600, Ashish Shah wrote:
> Hi,
>
> I am new. I am trying to figure out the right pogo pins to get in order to try to build a serial port for N900. But I am trying to decipher the docs in the wiki at the moment.
>
> Best,
>
> --
> Ashish Shah
Welcome!
I didn't succeed yet with making one, but that is not because it is
extremely difficult - I just happen to live where access to such stuff
isn't straightforward.
That said, if you have access to the materials, you can start with sre's
blog [0]. Additionally, chapter 3 of his thesis [1] has quite verbose
description of everything that is needed, as well as a diagram (Figure
3.3) clearly showing the location of the required pins.
We can also help you with any further information you may need.
Regards
Sicelo
[0] https://n900.elektranox.org/serial-adapter.html
[1] https://uol.de/f/2/dept/informatik/ag/svs/download/thesis/Reichel_Sebastian.pdf
next prev parent reply other threads:[~2022-11-19 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 19:33 Broken u-boot on n900 hw (possibly CONFIG_POSITION_INDEPENDENT) Pali Rohár
2022-10-10 21:30 ` [maemo-leste] " Sicelo
2022-10-20 20:06 ` Pali Rohár
2022-10-21 19:09 ` Pali Rohár
2022-11-02 0:08 ` Pali Rohár
2022-11-09 20:33 ` Pali Rohár
2022-11-19 14:38 ` Ashish Shah
2022-11-19 18:24 ` Sicelo [this message]
2022-11-19 21:13 ` Pali Rohár
2022-11-20 15:33 ` Tom Rini
2022-11-20 16:13 ` Pali Rohár
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y3kfbxO8HzBAVlou@tp440p.steeds.sam \
--to=absicsz@gmail.com \
--cc=ashish@emailuser.net \
--cc=maemo-leste@lists.dyne.org \
--cc=pali@kernel.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox