Recherche avancée

Sur d’autres sites (6756)

• Notes on Linux for Dreamcast

  23 février 2011, par Multimedia Mike — Sega Dreamcast, VP8

  I wanted to write down some notes about compiling Linux on Dreamcast (which I have yet to follow through to success). But before I do, allow me to follow up on my last post where I got Google’s libvpx library decoding VP8 video on the DC. Remember when I said the graphics hardware could only process variations of RGB color formats ? I was mistaken. Reading over some old documentation, I noticed that the DC’s PowerVR hardware can also handle packed YUV textures (UYVY, specifically) :

  
  
  

  The video looks pretty sharp in the small photo. Up close, less so, due to the low resolution and high quantization of the test vector combined with the naive chroma upscaling. For the curious, the grey box surrounding the image highlights the 256-square texture that the video frame gets plotted on. Texture dimensions have to be powers of 2.

  Notes on Linux for Dreamcast
  I’ve occasionally dabbled with Linux on my Dreamcast. There’s an ancient (circa 2001) distro based around a build of kernel 2.4.5 out there. But I wanted to try to get something more current compiled. Thus far, I have figured out how to cross compile kernels pretty handily but have been unsuccessful in making them run.

  Here are notes are the compilation portion :
  

  • kernel.org provides a very useful set of cross compiling toolchains
  • get the gcc 4.5.1 cross toolchain for SH-4 (the gcc 4.3.3 one won’t work because the binutils is too old ; it will fail to assemble certain instructions as described in this post)
  • working off of Linux kernel 2.6.37, edit the top-level Makefile ; find the ARCH and CROSS_COMPILE variables and set appropriately :

    ARCH ?= sh
    CROSS_COMPILE ?= /path/to/gcc-4.5.1-nolibc/sh4-linux/bin/sh4-linux-
    

  • $ make dreamcast_defconfig
  • $ make menuconfig ... if any changes to the default configuration are desired
  • manually edit arch/sh/Makefile, changing :

    cflags-$(CONFIG_CPU_SH4) := $(call cc-option,-m4,) \
            $(call cc-option,-mno-implicit-fp,-m4-nofpu)
    

    to :

    cflags-$(CONFIG_CPU_SH4) := $(call cc-option,-m4,) \
            $(call cc-option,-mno-implicit-fp)
    

    I.e., remove the '-m4-nofpu' option. According to the gcc man page, this will "Generate code for the SH4 without a floating-point unit." Why this is a default is a mystery since the DC’s SH-4 has an FPU and compilation fails when enabling this option.

  • On that note, I was always under the impression that the DC sported an SH-4 CPU with the model number SH7750. According to this LinuxSH wiki page as well as the Linux kernel help, it actually has an SH7091 variant. This photo of the physical DC hardware corroborates the model number.
  • $ make ... to build a Linux kernel for the Sega Dreamcast

  Running
  So I can compile the kernel but running the kernel (the resulting vmlinux ELF file) gives me trouble. The default kernel ELF file reports an entry point of 0x8c002000. Attempting to upload this through the serial uploading facility I have available to me triggers a system reset almost immediately, probably because that’s the same place that the bootloader calls home. I have attempted to alter the starting address via ’make menuconfig’ -> System type -> Memory management options -> Physical memory start address. This allows the upload to complete but it still does not run. It’s worth noting that the 2.4.5 vmlinux file from the old distribution can be executed when uploaded through the serial loader, and it begins at 0x8c210000.

• Rails 3 : How can I make Paperclip-FFMPEG work ?

  9 novembre 2011, par remino

  I have Rails 3.0.3 with these gems :

  • delayed_job 2.1.4
  • delayed_paperclip 0.7.1
  • paperclip 2.3.16
  • paperclip-ffmpeg 0.7.0

  (This combination is very specific. Some newer gems will not work with others.)

  Here's my Video model :

  class Video < Upload
  
    has_attached_file :file, :default_style => :view, :processors => [:ffmpeg],
  
      :url => '/system/:class/:attachment/:id/:style/:basename.:extension',
  
      :path => ':rails_root/public/system/:class/:attachment/:id/:style' \
  
        + '/:basename.:extension',
  
      :default_url => '/images/en/processing.png',
  
      :styles => {
  
        :mp4video => { :geometry => '520x390', :format => 'mp4',
  
          :convert_options => { :output => { :vcodec => 'libx264',
  
            :vpre => 'ipod640', :b => '250k', :bt => '50k',
  
            :acodec => 'libfaac', :ab => '56k', :ac => 2 } } },
  
        :oggvideo => { :geometry => '520x390', :format => 'ogg',
  
          :convert_options => { :output => { :vcodec => 'libtheora',
  
            :b => '250k', :bt => '50k', :acodec => 'libvorbis',
  
            :ab => '56k', :ac => 2 } } },
  
        :view => { :geometry => '520x390', :format => 'jpg', :time => 1 },
  
        :preview => { :geometry => '160x120', :format => 'jpg', :time => 1 }
  
      }
  
    validates_attachment_content_type :file, :content_type => VIDEOTYPES,
  
      :if => Proc.new { |upload| upload.file.file? }
  
    process_in_background :file
  
  end

  When creating a new Video object with attachment, the original is saved, but no conversion will be done. Even calling Video.last.file.reprocess! won't to a thing except returning true. (Not sure what "true" means in this case as it didn't work.)

  I tried hardcoding the path to ffmpeg in Paperclip::options[:command_path]. I even tried deleting the paperclip-ffmpeg.rb file and replacing it with a blank file. Really thinking I'd get an exception by doing the later, instead, I simply got "true" again.

  It feels like the paperclip-ffmpeg.rb is being loaded, because it is required by config/application.rb, but nothing is called in it when trying to generate a thumbnail or convert a video.

  Can anyone help me with this ? Thanks in advance !

• Set viewport width to device width.

  8 mars 2012, par Sebastian Tschan

  m css/jquery.fileupload-ui.css m index.html m test/index.html Set viewport width to device width. CSS fixes for mobile devices with screen sizes