From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] imx: add module fuse support
Date: Wed, 24 Jul 2019 21:39:10 +0200 [thread overview]
Message-ID: <20190724213910.17005e7e@jawa> (raw)
In-Reply-To: <765d0d36-f990-f301-5571-bc33b92e06b4@kontron.de>
Hi Frieder,
> >>
> >> Is there any markings on the SoC? (like MX6ULXXXXXX) which
> >> indicates which SoC has enet and which doesn't have one?
>
> Yes, you can look in the datasheets. For i.MX6ULL ([1], [2]) for
> example, there is a table in chapter 1.1, which describes the
> features for the different types and the corresponding part numbers.
> And the part numbers are printed on the chips.
Thanks for the info.
>
> Regards,
> Frieder
>
> [1] https://www.nxp.com/docs/en/data-sheet/IMX6ULLCEC.pdf
> [2] https://www.nxp.com/docs/en/data-sheet/IMX6ULLIEC.pdf
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190724/baa786c3/attachment.sig>
prev parent reply other threads:[~2019-07-24 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 3:22 [U-Boot] [PATCH 1/4] imx: add module fuse support Peng Fan
2019-07-19 3:22 ` [U-Boot] [PATCH 2/4] i2c: mxc: add fuse check Peng Fan
2019-07-19 3:22 ` [U-Boot] [PATCH 3/4] usb: mx6: " Peng Fan
2019-07-19 3:22 ` [U-Boot] [PATCH 4/4] net: fec: " Peng Fan
2019-07-23 3:27 ` Joe Hershberger
2019-07-23 5:46 ` Peng Fan
2019-07-24 7:48 ` [U-Boot] [PATCH 1/4] imx: add module fuse support Lukasz Majewski
2019-07-24 7:52 ` Peng Fan
2019-07-24 10:05 ` Lukasz Majewski
2019-07-24 12:12 ` Peng Fan
2019-07-24 18:12 ` Schrempf Frieder
2019-07-24 19:39 ` Lukasz Majewski [this message]
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=20190724213910.17005e7e@jawa \
--to=lukma@denx.de \
--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