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

LGPL license violation reported by upstream FFmpeg #530

Open
nyanmisaka opened this issue Feb 23, 2024 · 13 comments
Open

LGPL license violation reported by upstream FFmpeg #530

nyanmisaka opened this issue Feb 23, 2024 · 13 comments

Comments

@nyanmisaka
Copy link
Contributor

Upstream FFmpeg on Twitter reported an LGPL license violation in MPP's code. If this was due to an oversight, it's best to correct it promptly to avoid further harming Rockchip's reputation in the open source community.

Hey
@IloveRockchip
, blatantly copy and pasting FFmpeg code into your driver and changing the licence in violation of the LGPL is not cool:
https://github.com/rockchip-linux/mpp/blob/fdeb8c378b79d4b4ef80457e4431815de89dc417/mpp/codec/dec/av1/av1d_cbs.c

1

@JoshuaDoes
Copy link

I should note, if the project contributors are aware of any other misuse of licensed open source code, it's best to include removing or fixing those areas too. Chances are this isn't the only example, if that were the case.

@elenril
Copy link

elenril commented Feb 23, 2024

From a brief look, I see a large number of clear violations. At least

  • mpp/codec/dec/av1/av1d_codec.h
  • mpp/codec/dec/av1/av1d_cbs.c
  • mpp/codec/dec/av1/av1d_cbs.h
  • mpp/codec/dec/av1/av1d_parser2_syntax.c
  • mpp/codec/dec/h265/h265d_codec.h
  • mpp/codec/dec/h265/h265d_parser.c
  • mpp/codec/dec/h265/h265d_ps.c
  • mpp/codec/dec/vp9/vp9d_codec.h
  • mpp/codec/dec/vp9/vp9d_parser.c
  • mpp/codec/dec/vp9/vp9data.h
  • mpp/codec/dec/vp9/vpx_rac.c
  • mpp/codec/dec/vp9/vpx_rac.h

are clearly derived from libavcodec source code, as is obvious from the same code structure and naming, identical comments in the code, and sometimes even references to av_* functions and libavcodec.

@nyanmisaka
Copy link
Contributor Author

This violation was caused by the developer's insufficient understanding of the compatibility between licenses. They apologized deeply and said they would fix it as soon as possible and strengthen their learning about open source licenses. They also thank the open source community for pointing these out and welcome any suggestions and guidance.

https://twitter.com/HermanChen1982/status/1761231278962364815 commented by @HermanChen at Rockchip

image

@hbiyik
Copy link

hbiyik commented Apr 15, 2024

So new release, still no change, or the changes pushed not counted as release:)

@nyanmisaka
Copy link
Contributor Author

So new release, still no change, or the changes pushed not counted as release:)

Where’s the new release? IMHO they use tag as public release.

https://github.com/rockchip-linux/mpp/tags

@hbiyik
Copy link

hbiyik commented Apr 15, 2024

Yeah there was bunch of new commits in the repo i thought it was a realease, seems not. Still im oss policing around :)

@HermanChen
Copy link
Collaborator

So far we are fixing rk3576 issues. Quit a busy time.
The license issue is delayed.

@hbiyik
Copy link

hbiyik commented Jul 1, 2024

so still not doing anything about it?

@ramiropolla
Copy link

ramiropolla commented Jul 1, 2024

So far we are fixing rk3576 issues. Quit a busy time. The license issue is delayed.

Please fix this license violation as soon as possible (it should be top priority, above any other issues you have), otherwise we will have to issue a takedown request to github.

@wenyue7
Copy link

wenyue7 commented Jul 2, 2024

Thank you for your kind reminder, we are working on it

@HermanChen
Copy link
Collaborator

The hevc, vp9 and av1 code will be fixed.

@nosoul78
Copy link

nosoul78 commented Jul 2, 2024

Please fix this license violation as soon as possible (it should be top priority, above any other issues you have), otherwise we will have to issue a takedown request to github.

@ramiropolla FWIW they've had over 5 months to CTRL+H the misleading licenses.

I find it...interesting how people still bother to do free work for this kind of hardware (after so so many years) when this is all they get in return.

@hbiyik
Copy link

hbiyik commented Oct 28, 2024

@HermanChen any update?

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

No branches or pull requests

8 participants