Announcement

Collapse
No announcement yet.

Months After Being Deprecated, Linux Ready To Say Goodbye To WiMAX

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Hibbelharry
    replied
    This is just one more silly effort by the wayland people trying to kill off network connectivity so noone misses X11 network transparency.

    Leave a comment:


  • tg--
    replied
    Originally posted by torsionbar28 View Post
    I can't think of any end-user use cases for WiMax that wouldn't be better served by Starlink. I don't think anyone is going to miss this code.
    I can think of a bunch:
    - any mobile device
    - any handheld/portable device
    - any affordable device
    - any indoor application without the possibility for a large external dish/array
    - any power limited application (1 Watt vs 100 Watts)

    Comparing Starlink to Wimax is like comparing a Helipad to a Car.
    Both are transport technologies, but they're not in the same category and neither can really replace the other.

    Leave a comment:


  • kcrudup
    replied
    Originally posted by Vistaus View Post
    ... this is the Linux and esp. Phoronix community, so there will always be at least one person who's going to miss old code
    Yup, came here for the inevitable "my old shit needs this!" comment- WiMAX must truly be out of use, as there wasn't a single one!

    Leave a comment:


  • Delgarde
    replied
    Originally posted by Viki Ai View Post
    It is mostly about if someone is willing to maintain the code. With a bit of how-much-the-code-interacts/interferes-with-other-code thrown in for flavor.

    N64 Kernel passes both (for now) because the codebase it is (for now) being actively maintained by someone(s), and it doesn't appear to cause any significant inter-dependency issues with the rest of the stack (you could even pull the "supporting-weird-architectures-can-draw-out-obscure-bugs" argument, to a degree).
    Yeah, that covers it pretty well... as long as someone is taking responsibility for it and it doesn't significantly impact more important parts of the kernel, they're not particularly fussy about support for niche architectures. But conversely, WiMax doesn't seem to have anyone interested in keeping it alive, and its continued existence becomes a burden for people maintaining adjacent parts of the networking stack... there's a real incentive to get rid of it.

    Leave a comment:


  • wizard69
    replied
    Good thing the article mentioned what WiMAX was, it is a forgotten tech around here.

    Leave a comment:


  • Nth_man
    replied
    Originally posted by skeevy420 View Post
    DIE
    By my hand
    I creep across the land
    Riding Intel's van

    I'm WiMAX's death? :-)
    Last edited by Nth_man; 21 March 2021, 07:02 PM.

    Leave a comment:


  • skeevy420
    replied
    DIE
    By my hand
    I creep across the land
    Riding Intel's van

    Leave a comment:


  • fafreeman
    replied
    Originally posted by Vistaus View Post

    You're wrong: this is the Linux and esp. Phoronix community, so there will always be at least one person who's going to miss old code
    NOOOO NOT THE WIMAXERINO! how else am i going to drive my internets to the max now?

    Leave a comment:


  • Viki Ai
    replied
    Originally posted by antnythr View Post
    I've seen a couple of posts here lately about code being pulled out from the kernel, but also that someone is busy working on bringing N64 support to the kernel.

    Are there a certain number of users of a particular code that are needed for software to be included in the kernel? Or is it just a matter of someone being willing to maintain it and it'll be included? The N64 support was interesting and I didn't know if the developer needs to justify their use case to be included, or if can just develop the software and as long as the quality is there and they are available to maintain support, is inclusion in the kernel just a given?
    It is mostly about if someone is willing to maintain the code. With a bit of how-much-the-code-interacts/interferes-with-other-code thrown in for flavor.

    N64 Kernel passes both (for now) because the codebase it is (for now) being actively maintained by someone(s), and it doesn't appear to cause any significant inter-dependency issues with the rest of the stack (you could even pull the "supporting-weird-architectures-can-draw-out-obscure-bugs" argument, to a degree).

    Leave a comment:


  • antnythr
    replied
    I've seen a couple of posts here lately about code being pulled out from the kernel, but also that someone is busy working on bringing N64 support to the kernel.

    Are there a certain number of users of a particular code that are needed for software to be included in the kernel? Or is it just a matter of someone being willing to maintain it and it'll be included? The N64 support was interesting and I didn't know if the developer needs to justify their use case to be included, or if can just develop the software and as long as the quality is there and they are available to maintain support, is inclusion in the kernel just a given?

    Leave a comment:

Working...
X