#46 closed task (duplicate)
Make sure that the compatibility mapping from course (digital / analogue) to HAL technology related to the underlaying os is given
| Reported by: | Florian Roth | Owned by: | nobody |
|---|---|---|---|
| Priority: | major | Milestone: | MS1: First release (1.0.0) |
| Component: | hal | Version: | pre-1.0 |
| Keywords: | Cc: |
Description
Currently in my opinon we have the following relationships:
Digital Course -> Windows -> No HAL (only simulation)
That means we have to generate sensor data by our selfes.
Digital Course -> Linux -> lib42 HAL
Analogue Couse -> Windows -> Analogue and/or Bluerider
Analogue Couse -> Linux -> Analogue and/or Bluerider
Change History (4)
comment:1 Changed 16 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
comment:2 Changed 16 years ago by
| Milestone: | MS3: Input device and slot car track support → MS1: First usable version |
|---|
comment:3 Changed 16 years ago by
| Owner: | changed from somebody to nobody |
|---|
Batch reassigned all tickets owned by the virtual user 'somebody' to the virtual user 'nobody'.
comment:4 Changed 16 years ago by
| Component: | unspecified → hal |
|---|
Note: See
TracTickets for help on using
tickets.
Batch moved MS3 (input device/technology integration) to MS1 (first working version).