cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Xiling MPSOC -- was Re:  CIP IRC weekly meeting today
Date: Tue, 1 Oct 2019 10:47:49 +0200	[thread overview]
Message-ID: <20191001084749.GA1630@amd> (raw)
In-Reply-To: <CAFa_k0gKU3eudKOK-txbprBA4=B+9RnJXs5VX18GXxvr2SqPYg@mail.gmail.com>

Hi!

> At the CIP kernel meeting, there was the following conversation regarding the Cybertrust proposal.
> (BTW, 'masashi910' is me. )
> 
> [18:43] <pave1> masashi910: We don't need working version at the moment. But if you could mail the patches, or post pointer for them, or at least diffstat... That would help.
> [18:44] <masashi910> pavel: Thanks. Our work is currently being done locally. I will discuss our team how to share the patches with you.
> 
> The current work which contains all CIP kernel files is compiled into a tar ball, and I uploaded the ball under the following repository.
> https://github.com/masashi910/tmp-cip-xilinx-mpsoc/

Thanks, let me take a look.

For the record, way to get the files is

git clone https://github.com/masashi910/tmp-cip-xilinx-mpsoc.git
cd tmp-cip*
cat linux-4.19.56.tar.bz2.00* > linux.tar.bz2
tar xjvf linux.tar.bz2

Unfortunately, git commands can not be used in that repository, since
it points to alternates somewhere.

I diffed that against v4.19.56; which unfortunately produced unclean
diff as it now also includes the -cip changes. I quickly reviewed and
hand-edited the diff.

I notice this includes staging drivers. 

+obj-$(CONFIG_XILINX_APF)       += apf/
+obj-$(CONFIG_XILINX_FCLK)      += fclk/

I believe you should get those reviewed and moved outside of staging
before attempting to backport them.

Otherwise I don't see anything too scary.

     		      	      	  	  	     	     	     Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191001/c0e204ea/attachment.sig>

  reply	other threads:[~2019-10-01  8:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26  2:46 [cip-dev] CIP IRC weekly meeting today SZ Lin (林上智)
     [not found] ` <CAFa_k0gBzv-2bOF_pGbpvZQyQ1ocEu-bsBNT_JsWi12cxrK-Pg@mail.gmail.com>
2019-09-26  3:01   ` masashi.kudo at cybertrust.co.jp
2019-09-28  4:30     ` masashi.kudo at cybertrust.co.jp
2019-09-30  7:19       ` Chris Paterson
2019-10-01  2:47     ` masashi.kudo at cybertrust.co.jp
2019-10-01  8:47       ` Pavel Machek [this message]
2019-10-01  9:19         ` [cip-dev] Xiling MPSOC -- was " Pavel Machek
2019-10-01 12:41           ` masashi.kudo at cybertrust.co.jp
2019-10-01 16:02             ` Jan Kiszka
2019-10-02  3:00         ` masashi.kudo at cybertrust.co.jp

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=20191001084749.GA1630@amd \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    /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;
as well as URLs for NNTP newsgroup(s).