> -----Original Message----- > From: Mike Looijmans [mailto:[email protected]] > Sent: Thursday, November 30, 2017 2:04 AM > To: Syed Syed <[email protected]>; Manjukumar Harthikote Matha > <[email protected]>; Martin Siegumfeldt <[email protected]>; meta- > [email protected] > Subject: Re: [meta-xilinx] QSPI Issues related to Linux 4.9 > > On 29-11-17 09:29, Syed Syed wrote: > > [email protected] is internal to Xilinx. You should use [email protected]. > > It is still in > active state. I don’t know why no-one acknowledged your patches there. Can you > re-try? I will try to make sure it reaches right folks at Xilinx. Appreciate > your efforts. > > > > I resent the series, to [email protected], with a BCC to a private e-mail > account and > verified that all three arrived safely. > > If you did not receive it, please complain loudly to your IT department. >
We have to now, because we never got the patches :) I have opened an internal CR to track and get these patches applied, if we cannot apply it for 4.9 we will definitely address it in the next kernel upgrade version. Thanks, Manju > > > Thanks > > -syed > > > >> > > Kind regards, > > Mike Looijmans > System Expert > > TOPIC Products > Materiaalweg 4, NL-5681 RJ Best > Postbus 440, NL-5680 AK Best > Telefoon: +31 (0) 499 33 69 79 > E-mail: [email protected] > Website: www.topicproducts.com > > Please consider the environment before printing this e-mail > > > > -----Original Message----- > >> From: [email protected] [mailto:meta-xilinx- > >> [email protected]] On Behalf Of Mike Looijmans > >> Sent: Wednesday, November 29, 2017 11:54 AM > >> To: Manjukumar Harthikote Matha <[email protected]>; Martin > >> Siegumfeldt <[email protected]>; [email protected] > >> Subject: Re: [meta-xilinx] QSPI Issues related to Linux 4.9 > >> > >> I re-sent the three patches as series to [email protected] with a CC to > >> you. > >> > >> Mike. > >> > >> On 28-11-17 19:56, Manjukumar Harthikote Matha wrote: > >>> Hi Mike, > >>> > >>> Thanks for your work, please send patches to [email protected] > >>> > >>> Thanks, > >>> Manju > >>> > >>>> > >> > >> Kind regards, > >> > >> Mike Looijmans > >> System Expert > >> > >> TOPIC Products > >> Materiaalweg 4, NL-5681 RJ Best > >> Postbus 440, NL-5680 AK Best > >> Telefoon: +31 (0) 499 33 69 79 > >> E-mail: [email protected] > >> Website: www.topicproducts.com > >> > >> Please consider the environment before printing this e-mail > >> > >> > >> > >> -----Original Message----- > >>>> From: [email protected] [mailto:meta-xilinx- > >>>> [email protected]] On Behalf Of Mike Looijmans > >>>> Sent: Monday, November 27, 2017 2:57 AM > >>>> To: Martin Siegumfeldt <[email protected]>; > >>>> [email protected] > >>>> Subject: Re: [meta-xilinx] QSPI Issues related to Linux 4.9 > >>>> > >>>> There are several bugs (at least 3) in the Xilinx tree relating to > >>>> QSPI, I implemented fixes in our tree and sent patches to > >>>> [email protected] (with CC to several Xilinx people). > >>>> > >>>> I did not receive any feedback so far. > >>>> > >>>> I get the impression that the [email protected] e-mail is no longer in use. > >>>> Better suggestions are welcome. > >>>> > >>>> The QSPI code from Xilinx is not part of mainline Linux (and for > >>>> good reason it seems), so sending patches to mainline linux is pointless. > >>>> > >>>> (If you're designing Zynq boards, my advice for now is to steer > >>>> away from the dual-qspi config, it's almost useless on the Zynq and > >>>> forces you to use Xilinx' tree instead of mainline) > >>>> > >>>> > >>>> > >>>> On 24-11-17 14:02, Martin Siegumfeldt wrote: > >>>>> Hi, > >>>>> > >>>>> I recently updated the Linux kernel for a custom board based on > >>>>> z7k from Xilinx > >>>> version 4.6 to 4.9, and spend a few days debugging issues related > >>>> to the QSPI flash (n25q512a13). By coincidence I stumbled upon > >>>> https://github.com/topic-embedded- > >>>> > >> products/linux/commit/8f89736e4e4c116b442f56b3414c33b36f99bc18#diff- > >>>> 49f4e70fe9e60ff773b57164b9e03dbb (thanks Mike) which resolved the > >>>> issue. It looks like this commit has been left out during the 4.9 > >>>> transition. Since I am apparently not the only one encountering > >>>> this issue I wonder if this is planned fixed upstream (upstream as > >>>> in the Xilinx fork I mean) > >>>>> > >>>>> Thanks, > >>>>> Martin > >>>>> > >>>> > >>>> > >>>> > >>>> Kind regards, > >>>> > >>>> Mike Looijmans > >>>> System Expert > >>>> > >>>> TOPIC Products > >>>> Materiaalweg 4, NL-5681 RJ Best > >>>> Postbus 440, NL-5680 AK Best > >>>> Telefoon: +31 (0) 499 33 69 79 > >>>> E-mail: [email protected] > >>>> Website: www.topicproducts.com > >>>> > >>>> Please consider the environment before printing this e-mail > >>>> > >>>> > >>>> > >>>> -- > >>>> _______________________________________________ > >>>> meta-xilinx mailing list > >>>> [email protected] > >>>> https://lists.yoctoproject.org/listinfo/meta-xilinx > >> > >> -- > >> _______________________________________________ > >> meta-xilinx mailing list > >> [email protected] > >> https://lists.yoctoproject.org/listinfo/meta-xilinx -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
