From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Features backports
Date: Tue, 29 Nov 2016 10:01:38 +0100 [thread overview]
Message-ID: <583D43F2.50301@codethink.co.uk> (raw)
In-Reply-To: <390B4EACA1A32748BA6BC7F859F7D71655274E10@GSjpTKYDCembx31.service.hitachi.net>
Hi,
On 29/11/16 03:57, ???? / KOGUCHI?TAKUO wrote:
> Hi,
>
> Regarding to Altera Socfpga Cyclone V, we might want to backport from 4.9;
> - L2cache ECC(./arch/arm/mm/cache-l2x0.c)
> - QSPI Flash controller(drivers/mtd/spi-nor/cadence-quadspi.c)
>
> 4.9 is still missing the followings which exist in the verdor tree(linux-socfpga);
> - HPS2FPGA(drivers/fpga/altera-hps2fpga.c)
> - NAND Flash controller(drivers/mtd/nand/denali_dt.c)
> I hope we can encourage Altera to push these features upstream or do it ourselves.
I think we have a good chance once they see we are testing Beaglebone
Black in the open. That would be a good opportunity we might add value
to them.
Definitely I would talk to them before. If they are not pushing the
patches upstream, it would be a good question why.
>
> Takuo
>
>
>> -----Original Message-----
>> From: cip-dev-bounces at lists.cip-project.org
>> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Agustin Benito
>> Bethencourt
>> Sent: Friday, November 18, 2016 9:26 PM
>> To: cip-dev at lists.cip-project.org
>> Subject: [!][cip-dev] Features backports
>>
>> Hi,
>>
>> as you probably know, the more features we backport, the higher will be the
>> maintenance cost overtime so as a strategy, we need to be very
>> conservative.
>>
>> I sent a mail some days ago about the features backported already by Linaro
>> for their LSK (Linaro Stable Kernel) for your evaluation. I bring today some
>> potential backports related with security features and hardware support that
>> has been identified by Ben H.
>>
>> * UBSAN support:
>> <https://git.kernel.org/linus/c6d308534aef6c99904bf5862066360ae067abc4
>>>
>>
>> * Increased user-space ASLR range for ARM:
>> <https://lwn.net/Articles/667790/>
>>
>> * Page poisoning on free:
>> <https://git.kernel.org/linus/8823b1dbc05fab1a8bec275eeae4709257c2661
>> d>,
>> <https://git.kernel.org/linus/1414c7f4f7d72d138fff35f00151d15749b5beda>
>>
>> * SLAB/SLUB freelist randomisation
>>
>> * Hardened usercopy
>>
>> * Do Members use SLUB? if not, we should take a look at KASAN support for
>> SLAB
>>
>> * drm/tilcdc update? (many bug fixes post-4.4)
>>
>> * AM33xx RTC support:
>>
>> <https://git.kernel.org/linus/461932dfb54ebaf7da438fd8b769a01ce97a9360
>>> ,
>> <https://git.kernel.org/linus/b5a553c08bec14a058501df3fa6eb39f63f00a98>
>>
>>
>> Best Regards
>> --
>> Agustin Benito Bethencourt
>> Principal Consultant - FOSS at Codethink agustin.benito at codethink.co.uk
>> _______________________________________________
>> cip-dev mailing list
>> cip-dev at lists.cip-project.org
>> https://lists.cip-project.org/mailman/listinfo/cip-dev
>
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next prev parent reply other threads:[~2016-11-29 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 12:26 [cip-dev] Features backports Agustin Benito Bethencourt
2016-11-28 13:47 ` Jan Kiszka
2016-11-28 14:17 ` Agustin Benito Bethencourt
2016-11-29 2:57 ` 小口琢夫 / KOGUCHI,TAKUO
2016-11-29 9:01 ` Agustin Benito Bethencourt [this message]
2016-12-02 8:44 ` KOBAYASHI Yoshitake
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=583D43F2.50301@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--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 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.