Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update use of long-deprecated pci_ dma API code to the more generic d… #17

Merged
merged 1 commit into from Aug 14, 2023

Conversation

jkroonza
Copy link
Contributor

…ma_ API.

I can trace back dma_ to at least kernel 3.2 and I've found mention of this generic API around 2002 already, so this should work on some really old kernels too.

The only question is whether all uses actually require GFP_ATOMIC, but since pci_alloc_consistent used that, just stick with it as I don't know how to verify this.

…ma_ API.

I can trace back dma_ to at least kernel 3.2 and I've found mention of
this generic API around 2002 already, so this should work on some really
old kernels too.

The only question is whether all uses actually require GFP_ATOMIC, but
since pci_alloc_consistent used that, just stick with it as I don't know
how to verify this.

Signed-off-by: Jaco Kroon <jaco@uls.co.za>
@InterLinked1
Copy link
Contributor

I think the next branch already has this fix?
dbb4310

@jkroonza
Copy link
Contributor Author

I think the next branch already has this fix? dbb4310

It's possible.

Since the dma_* functions has been around since a very long time, is it really preferred to conditionally wrap again, or rather just convert to the appropriate APIs? I get that it's desirable to keep the module working with older kernels too, but to wrap it when the converted to APIs have been around almost as long as the original APIs?

@InterLinked1
Copy link
Contributor

I think they conditionally wrapped it because that was the "quick and dirty fix". It's clear that DAHDI Linux hasn't been properly maintained in a long time, and still isn't.

Regardless, you should base your patches off the next or 3.3.0 branches instead of the master branch, since the master branch is significantly out of date. I don't know when they'll reconcile them as there's been no activity for half a year now.

@push143smart push143smart merged commit ee13cb2 into asterisk:master Aug 14, 2023
1 check was pending
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants