Re: About PCIE MHI driver build question!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 09, 2019 at 06:51:25AM +0000, 桂永林 wrote:
> Hi,
>    I had got a Qualcomm MHI PCIE driver which had released on kernel_xiaomi_sm8150/drivers/bus/mhi/ path. But I can't build the driver and the kernel. If someone can help me give me a guide about how to build the MHI driver?
>    I use bellow command to clone the project:
>       git clone -b https://github.com/Demon000/kernel_xiaomi_sm8150/tree/lineage-17.0
>    The MHI driver located at kernel_xiaomi_sm8150/drivers/bus/mhi/ path.
> Thanks!
> Opera
> 

Hi Opera,

Unfortunately that Github URL relates to a fork of an earlier mainline kernel,
the driver you refer to was added in that fork and not the mainline kernel. So
it's unlikely anyone here will know anything about it. I'd recommend you find
out who added that driver or who can provide support for that Github fork.

The mainline kernel does appear to have support for PCI for the SM8150-mtp,
see if arch/arm64/boot/dts/qcom/sm8150-mtp.dts fits your needs.

Thanks,

Andrew Murray

> 
> 
> 
> -----邮件原件-----
> 发件人: gregkh@xxxxxxxxxxxxxxxxxxx [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] 
> 发送时间: 2019年10月9日 14:40
> 收件人: 桂永林 <opera.gui@xxxxxxxxxxx>
> 主题: Re: 答复: About MHI driver build question!
> 
> Hi,
> 
> This is the friendly email-bot of Greg Kroah-Hartman's inbox.  I've detected that you have sent him a direct question that might be better sent to a public mailing list which is much faster in responding to questions than Greg normally is.
> 
> Please try asking one of the following mailing lists for your questions:
> 
>   For udev and hotplug related questions, please ask on the
>   linux-hotplug@xxxxxxxxxxxxxxx mailing list
> 
>   For USB related questions, please ask on the linux-usb@xxxxxxxxxxxxxxx
>   mailing list
> 
>   For PCI related questions, please ask on the
>   linux-pci@xxxxxxxxxxxxxxx or linux-kernel@xxxxxxxxxxxxxxx mailing
>   lists
> 
>   For serial and tty related questions, please ask on the
>   linux-serial@xxxxxxxxxxxxxxx mailing list.
> 
>   For staging tree related questions, please ask on the
>   devel@xxxxxxxxxxxxxxxxxxxxxx mailing list.
> 
>   For general kernel related questions, please ask on the
>   kernelnewbies@xxxxxxxxxxxx or linux-kernel@xxxxxxxxxxxxxxx mailing
>   lists, depending on the type of question.  More basic, beginner
>   questions are better asked on the kernelnewbies list, after reading
>   the wiki at www.kernelnewbies.org.
> 
>   For Linux stable and longterm kernel release questions or patches to
>   be included in the stable or longterm kernel trees, please email
>   stable@xxxxxxxxxxxxxxx and Cc: the linux-kernel@xxxxxxxxxxxxxxx
>   mailing list so all of the stable kernel developers can be notified.
>   Also please read Documentation/process/stable-kernel-rules.rst in the
>   Linux kernel tree for the proper procedure to get patches accepted
>   into the stable or longterm kernel releases.
> 
> If you really want to ask Greg the question, please read the following two links as to why emailing a single person directly is usually not a good thing, and causes extra work on a single person:
> 	http://www.arm.linux.org.uk/news/?newsitem=11
> 	http://www.eyrie.org/~eagle/faqs/questions.html
> 
> After reading those messages, and you still feel that you want to email Greg instead of posting on a mailing list, then resend your message within 24 hours and it will go through to him.  But be forewarned, his email inbox currently looks like:
> 	912 messages in /home/greg/mail/INBOX/
> so it might be a while before he gets to the message.
> 
> Thank you for your understanding.
> 
> The email triggering this response has been automatically discarded.
> 
> thanks,
> 
> greg k-h's email bot



[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux