mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Porting Clause 45 PHY support to Barebox
Date: Fri, 26 Apr 2019 08:05:42 +0200	[thread overview]
Message-ID: <20190426060542.v4tybl24ngvfvf5v@pengutronix.de> (raw)
In-Reply-To: <0b4e8036-c8d2-abef-8ee7-d28994e552a8@gmail.com>

Hi Heiner,

On Thu, Apr 25, 2019 at 08:14:10PM +0200, Heiner Kallweit wrote:
> I'd like to port Clause 45 PHY support and more recent Linux phylib
> extensions to Barebox. Ideally it should be possible later to apply
> most Linux patches as-is on Barebox. Before I start two questions:
> 
> - Any guidelines what it typically takes to port Linux Kernel code
>   to Barebox? (I suppose at least removing mutexes + spinlocks, changing
>   all interrupts to polling)

Well yes, and that's about it. Sometimes you have to simplify the code,
sometimes you have to update some header files we have from Linux.

> - Especially regarding drivers/net/phy: any plans I should be aware of?

Much of the code is from Linux, but there's also much barebox original
code. I don't think the goal should be that it looks identically in the
end.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2019-04-26  6:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 18:14 Heiner Kallweit
2019-04-26  6:05 ` Sascha Hauer [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=20190426060542.v4tybl24ngvfvf5v@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=hkallweit1@gmail.com \
    /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