All of lore.kernel.org
 help / color / mirror / Atom feed
* [U-Boot] Quick question on i.MX8MQ
@ 2018-12-14 23:38 Sergey Kubushyn
  2018-12-15  3:25 ` Peng Fan
  0 siblings, 1 reply; 2+ messages in thread
From: Sergey Kubushyn @ 2018-12-14 23:38 UTC (permalink / raw)
  To: u-boot

I'm working on a i.MX8MQ port to our new device that is in very advanced
manufacturing stage. It is not a board but a self-contained terminal that is
going into production really soon (various molds are being done, mechanical
parts, wire harnesses and so on) so it would hardly be of general interest
i.e. I might submit some patches but not a new board.

I have one question right now for those involved and maintaning IMX tree.
What platform name is more likely to win, MX8M as in the main source tree
right now or IMX8M as in u-boot-imx.git?

It doesn't make a real difference but I would like to pick the more probable
one for my port so I won't have to add/remove that 'I' in a hundred
different files when u-boot-imx is merged into main tree.

I can use either one but would like to avoid that possible unnecessary job
later on when re-syncing with the main tree.

---
******************************************************************
*  KSI at home    KOI8 Net  < >  The impossible we do immediately.  *
*  Las Vegas   NV, USA   < >  Miracles require 24-hour notice.   *
******************************************************************

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [U-Boot] Quick question on i.MX8MQ
  2018-12-14 23:38 [U-Boot] Quick question on i.MX8MQ Sergey Kubushyn
@ 2018-12-15  3:25 ` Peng Fan
  0 siblings, 0 replies; 2+ messages in thread
From: Peng Fan @ 2018-12-15  3:25 UTC (permalink / raw)
  To: u-boot

Hi Sergey,

> -----Original Message-----
> From: Sergey Kubushyn [mailto:ksi at koi8.net]
> Sent: 2018年12月15日 7:38
> To: U-Boot list <u-boot@lists.denx.de>
> Cc: Peng Fan <peng.fan@nxp.com>
> Subject: Quick question on i.MX8MQ
> 
> I'm working on a i.MX8MQ port to our new device that is in very advanced
> manufacturing stage. It is not a board but a self-contained terminal that is
> going into production really soon (various molds are being done, mechanical
> parts, wire harnesses and so on) so it would hardly be of general interest i.e. I
> might submit some patches but not a new board.
> 
> I have one question right now for those involved and maintaning IMX tree.
> What platform name is more likely to win, MX8M as in the main source tree
> right now or IMX8M as in u-boot-imx.git?

IMX8M is preferred based on u-boot-imx tree. If Stefano's tree has not been synced
with the main upstream tree, you could use the main upstream tree, but I think
there should be no much difference, unless there are some patches queued in stefano's tree.

Just my practice, when I develop new patches, I'll check imx tree to see if there are patches
queued that might cause conflict if my patches are based on main master branch. If yes,
I'll work patches based on imx tree. If not, I'll work patches based on latest master branch.

Regards,
Peng.

> 
> It doesn't make a real difference but I would like to pick the more probable
> one for my port so I won't have to add/remove that 'I' in a hundred different
> files when u-boot-imx is merged into main tree.
> 
> I can use either one but would like to avoid that possible unnecessary job later
> on when re-syncing with the main tree.
> 
> ---
> **************************************************************
> ****
> *  KSI at home    KOI8 Net  < >  The impossible we do immediately.  *
> *  Las Vegas   NV, USA   < >  Miracles require 24-hour notice.   *
> **************************************************************
> ****

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-12-15  3:25 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-12-14 23:38 [U-Boot] Quick question on i.MX8MQ Sergey Kubushyn
2018-12-15  3:25 ` Peng Fan

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.