Linux - Kernel This forum is for all discussion relating to the Linux kernel. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-05-2021, 11:11 AM
|
#1
|
Member
Registered: Sep 2007
Posts: 300
Rep:
|
MSI enabled for an FPGA design without MSI support
Hello,
My FPGA is connected via PCIe to the host PC via a PCIe switch.
According to lspci, the FPGA is MSI enabled.
But - The FPGA has only legacy interrupt. The design does not support MSI at all.
Is it possible that somehow the PCIe switch "enabled" MSI ?
I ran:
Code:
rc=request_irq(pci_dev_s->irq, IrqHandlerPacket, IRQF_SHARED,"fio", NULL);
and got rc!=0
Thank you,
Zvika
|
|
|
11-05-2021, 01:09 PM
|
#2
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,441
|
Hold on there.
You're looking at your FPGA and you know what you're talking about, but we don't.
We'd need a pretty full explanation of the project & equipment, brand names, etc. You probably have at least one paranoid manager who would consider publishing research data on a public forum a firing offence. And then we have the term MSI, which means there's probably comms of some description going on. So by answering your post we could have the doubtful pleasure of working for your boss for free, while you get the credit, and the pay.
That said, there's underlying circuitry in an FPGA, and that is probably MSI capable, even if your design is not. I don't understand what code you ran or what relevance the answer has, and I'm one of the few hardware guys here.
|
|
1 members found this post helpful.
|
11-05-2021, 01:12 PM
|
#3
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,613
|
Quote:
Originally Posted by zvivered
Hello,
My FPGA is connected via PCIe to the host PC via a PCIe switch. According to lspci, the FPGA is MSI enabled. But - The FPGA has only legacy interrupt. The design does not support MSI at all. Is it possible that somehow the PCIe switch "enabled" MSI ? I ran:
Code:
rc=request_irq(pci_dev_s->irq, IrqHandlerPacket, IRQF_SHARED,"fio", NULL);
and got rc!=0
|
Check any of your other FPGA threads, going back at least *THIRTEEN YEARS* now:
https://www.linuxquestions.org/quest...rrupts-686156/
https://www.linuxquestions.org/quest...hw-4175608928/
https://www.linuxquestions.org/quest...-a-4175617636/
https://www.linuxquestions.org/quest...er-4175632357/
https://www.linuxquestions.org/quest...ng-4175671805/
https://www.linuxquestions.org/quest...a-disk-948858/
In your previous threads, you claimed to have an "FPGA specialist". You also are *STILL* providing next to zero information about your device, OS, etc., past the facts that this is a totally custom piece of hardware with a custom kernel (apparently).
*AGAIN*: - We do not have your custom hardware
- We do not have your custom OS
- We don't have ANY of your code
- We don't even know what this thing IS, or what it's supposed to do
Yet somehow you expect us to be able to help you?? You have been working on this for 13 years now...you rarely, if ever, post back or answer questions when asked. What do you think anyone is going to be able to help you with at this point, if you've had a 'team' working on this for 13 years and can't get it done?
|
|
1 members found this post helpful.
|
11-06-2021, 10:24 AM
|
#4
|
Member
Registered: Sep 2007
Posts: 300
Original Poster
Rep:
|
Hello,
Thank you for your reply.
I'm running centos 8.2 in root account.
Did not insert any driver I wrote yet (only centos default ones)
lspci reports MSI+
According to: https://www.kernel.org/doc/html/late...msi-howto.html
pci_disable_msi() is depracated and should not be used.
Should I try
Quote:
echo 0 > /sys/bus/pci/devices/$bridge/msi_bus
|
?
Can you please tell what extra info is required ?
Best regards,
Zvika
Last edited by zvivered; 11-06-2021 at 10:27 AM.
|
|
|
11-06-2021, 10:47 AM
|
#5
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,613
|
Quote:
Originally Posted by zvivered
Hello,Thank you for your reply.
I'm running centos 8.2 in root account. Did not insert any driver I wrote yet (only centos default ones) lspci reports MSI+
According to: https://www.kernel.org/doc/html/late...msi-howto.html
pci_disable_msi() is depracated and should not be used.
Should I try ?
Code:
echo 0 > /sys/bus/pci/devices/$bridge/msi_bus
|
You could have just TRIED IT faster than you posted back here, couldn't you???
Quote:
Can you please tell what extra info is required ?
|
You keep changing the story, and you have been *REPEATEDLY* asked to provide full information (for years at this point), and still don't, so what's the point in asking again?? And your story has now changed, since previously it's been a 'custom OS' for an embedded system, and yet now it's a stock CentOS 8 kernel.
*AGAIN*: you are running a custom OS, on custom hardware, using a custom kernel module. You *STILL* don't say what this mystery hardware is, what it does, or what this FPGA device is doing. You post no code, message(s)/error(s) that would let us know ANYTHING about your situation, yet you repeatedly are asking us for help. We *CANNOT* help you, since you have a 100% custom environment which you won't tell us anything about.
You have been working on this for *THIRTEEN YEARS* and claim to have an 'FPGA engineer' on your 'team'....so again, it's hard to see why you are posting on a forum when you have these resources available to you, and have all the knowledge of the environment which you *WILL NOT SHARE* with us.
|
|
|
11-06-2021, 12:41 PM
|
#6
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,441
|
He hasn't been working on the same project for 13 years, I'm pretty sure. But he does think we will provide help on something we know nothing about. I suppose I qualify as an FPGA engineer but I don't want his information. I'd have to spend days boning up before I could provide a few sentences of advice, free gratis and for nothing. And I'm retired.
If this is repeating for 13 years, why not report the thread? Oh, and if he can't do his job after 13 years, I'd fire that FPGA engineer  . Come to think about it, it's hard to see how zvivered is earning his keep either… but I'd defer to management on that one.
|
|
|
11-06-2021, 12:46 PM
|
#7
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,613
|
Quote:
Originally Posted by business_kid
He hasn't been working on the same project for 13 years, I'm pretty sure.
|
Don't know about that; his post history says it's either the same thing, or something VERY similar. Either way, the OP claims to have an FPGA engineer on their 'team', and have developed kernel modules for this custom embedded hardware before. So given all that, I can't imagine why they'd post on a forum, given...
Quote:
But he does think we will provide help on something we know nothing about.
|
..this?? Agreed totally; they haven't provided info, and keep reiterating "Can you tell me what extra info is needed?" thing when asked.
Quote:
I suppose I qualify as an FPGA engineer but I don't want his information. I'd have to spend days boning up before I could provide a few sentences of advice, free gratis and for nothing. And I'm retired.
If this is repeating for 13 years, why not report the thread? Oh, and if he can't do his job after 13 years, I'd fire that FPGA engineer . Come to think about it, it's hard to see how zvivered is earning his keep either… but I'd defer to management on that one.
|
I won't confirm or deny if I've had the same thoughts.
|
|
|
11-08-2021, 12:54 PM
|
#8
|
Member
Registered: Sep 2007
Posts: 300
Original Poster
Rep:
|
Hello,
I checked again. MSI in the FPGA is disabled (as it should be)
The reason request_irq returned an error is because the last parameter is NULL.
When I changed to :
rc=request_irq(pci_dev_s->irq, IrqHandlerPacket, IRQF_SHARED,"fio", pci_dev_s);
I got rc=0
Thank you,
Zvika
|
|
|
11-08-2021, 01:32 PM
|
#9
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,613
|
Quote:
Originally Posted by zvivered
Hello,
I checked again. MSI in the FPGA is disabled (as it should be) The reason request_irq returned an error is because the last parameter is NULL. When I changed to :
Code:
rc=request_irq(pci_dev_s->irq, IrqHandlerPacket, IRQF_SHARED,"fio", pci_dev_s);
I got rc=0
|
Great; and we still don't know anything about what you're doing, your code, hardware, or OS. So this information doesn't give us anything new, or let us understand anything further. Mark the thread SOLVED.
|
|
|
11-08-2021, 01:54 PM
|
#10
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,441
|
Next time, we'll let him sink without trace.
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 06:53 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|