AllSpice/ThunderScope
19
Fork 0
Files Issues 7 Design Reviews Releases Activity

Unique PCIe ID #223

New Issue
Open
opened 2022-01-04 04:14:12 +00:00 by profezzorn · 0 comments
profezzorn commented 2022-01-04 04:14:12 +00:00 (Migrated from github.com)
Copy Link

If at all possible, we should have our own PCIe ID for thunderscope.
Otherwise we are potentially setting ourselves up for driver collisions with other xilinx-based devices.

If at all possible, we should have our own PCIe ID for thunderscope. Otherwise we are potentially setting ourselves up for driver collisions with other xilinx-based devices.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Bug

Something's wrong… I can feel it

  
Cleanup

Non-critical cleanup actions

  
documentation

Improvements or additions to documentation

  
Driver

The glue that holds the firmware and software together!

  
duplicate

This issue or pull request already exists

  
Feature

New feature or request

  
Firmware

Everything to do with the FPGA code

  
glscopeclient

Issues with the glscopeclient integration

  
good first issue

Good for newcomers

  
Hardware

For the Hardware team

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
Linux

Related to Linux

  
performance

Relates to the performance of the system

  
question

Further information is requested

  
scopeserver

The software between the drivers and glscopeclient

  
Windows

Related to Windows

  
wontfix

This will not be worked on

No Label
Bug
Cleanup
documentation
Driver
duplicate
Feature
Firmware
glscopeclient
good first issue
Hardware
help wanted
invalid
Linux
performance
question
scopeserver
Windows
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AllSpice/ThunderScope#223
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?